Hello, I'm using Agilo 1.2.1 and Trac 0.11.7.
On my return from holiday I found a number of tickets had disappeared from a filter I'd defined to show the contents of a particular Milestone. On investigation I found that the Milestone had unintentionally been set to blank when a colleague had assigned these items to a different Sprint. All of our Sprints are associated with that particular Milestone. On starting to fix the affected tickets I encountered these issues: - When I used the Edit pane of the ticket to set the Milestone from blank to Release 1, this worked, but an additional unintended edit happened: the Sprint now became blank. - When I went back in to Edit and set the Sprint appropriately, the Milestone then became blank. - When I created a filter to show tickets with a blank Milestone, it listed several. However, when I opened each of those tickets in the View pane, it showed the Milestone field as non-blank, with the desired value, Release 1. However, when I used the Edit pane of these tickets, the drop-list showed the Milestone value as blank. So, it seems like there is a bug in which various parts of the user interface (the drop-list control in Edit, the simple text label in View, and the column contents in a filter) are not in agreement as to the data value. And it is possible for a user to hit the Submit Changes button and end up submitting completely unintended changes that lead to effective data loss. Yikes! Does anyone else have this problem? Thanks, Dominic Ashmole -- 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
