Today we release bug-fix updates to Agilo (0.9.0.2) and Agilo Pro 
(1.3.0.2). Besides several visual improvements and the introduction of 
the sidebar to the Whiteboard, this update fixes an issue where Bugs and 
Stories were not correctly returned to the global backlogs when removed 
from a sprint.

To find out whether you were affected, you can either enable backlogs 
with a milestone scope or follow the steps as outlined in this Group 
<http://groups.google.com/group/agilo/browse_thread/thread/f28690abbce98810/4bf2207211ad3ea9#4bf2207211ad3ea9>.

## Full List of Bug Fixes
 * When you remove the sprint of a story, the story appears in the 
   product backlog again (the internal milestone field is reset)
 * Pro: Display the Sidebar on the Whiteboard
 * When using the pound sign (#) in a sprint or milestone name, the 
   links on the Roadmap page were not displayed correctly
 * Fixed duplicate confirm commitment when the filtered burndown is 
   enabled
 * Fixed wrong error message when viewing a global backlog that the user 
   is not allowed to modify
 * Display Agilo Favicon instead of Trac's by default
 * Pro: Grey background when a ticket edit dialog opens works in all 
   browsers

More info on how to upgrade and where to download are available on our 
website:
http://www.agile42.com/cms/blog/2010/06/25/bugfix-release-agilo-
scrum-1302/


Best Regards
Agilo Developers

-- 
Follow Agilo on Twitter: http://twitter.com/agiloforscrum
Please support us by reviewing and voting on: 
http://userstories.com/products/8-agilo-for-scrum 
http://ohloh.net/p/agilo-scrum 
http://freshmeat.net/projects/agiloforscrum

You have received this message because you are subscribed to
the "Agilo for Scrum" Google Group. This group is focused on
supporting Agilo for Scrum users and is moderated by
agile42 GmbH <http://www.agile42.com>.

To post to this group, send email to [email protected]
To unsubscribe from this group, send an email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/agilo

Reply via email to