New Release of Agilo for Scrum 1.3.2
New Release of Agilo for Scrum It's the holiday season, and as usual we are proud to bring to you ...
- On
- 14 December 2010
- In
- Agilo
New Release of Agilo for Scrum
It's the holiday season, and as usual we are proud to bring to you a very special present: a new version of Agilo Pro 1.3.2 (and the Agilo Open Source edition).
New features and changes:
Configurable columns in the white board
You can configure up to two additional 'In Progress' columns on the White board. Each column correlates to a defined ticket status. To activate those, make sure you have a workflow configured that leads from and to these statuses. Then you can activate these extra columns by changing your trac.ini like this:
[agilo-whiteboard]
second_whiteboard_in_progress_ticket_status = <status_name>
second_whiteboard_in_progress_ticket_status.position = after
third_whiteboard_in_progress_ticket_status = <another_status_name>
third_whiteboard_in_progress_ticket_status.position = before

Additional changes and bugfixes
- Fixed saving due and completed dates on milestones in Trac 0.12.
- Fixed highlighting of search results in the Backlog on Firefox.
- Fixed Sprins with non-ASCII characters on Python 2.4 and using PostgreSQL.
- Fixed directory listing in source browser.
- Fixed an issue with persistent filters that could lead to all items in the backlog being filtered out on load until you changed the filter.
Known bug
Shortly before the release we received a bug report regarding the new option to include planned tickets in global backlogs (like the product backlog). If this is enabled, the order of tickets may be destroyed on in-place edits in the backlog. We're currently investigating this bug and will make sure the next release includes a fix. Until then our recommendation is to disable display of planned tickets.
Edit: This bug has been resolved in Agilo Pro 1.3.3.
How to Update
- Download the new version from the tools page and
unpack the zip file so you have a
binary_agilo-<version-number>_PRO-py<your python version>.eggfile. - Create a backup of your Agilo environment folder and your database (if you use sqlite, the database is just a file in your environment).
- Install the new version of Agilo:
easy_install binary_agilo-...(you might want to do that with thesudocommand on Linux) - If you used 'trac-admin deploy', you need to redeploy the static files (if you don't know what 'trac-admin deploy' does, just ignore it, it's just an additional optimization)
- Make sure you and the other users empty their browser cache before visiting the site.
More information about upgrading can be found in our upgrade guide

Discussion No comments yet. Be first to comment!