Hi,
I can now reproduce the problem as well: If you change the milestone
from X -> '' in a milestone backlog, the requirement jumps to the bottom.
I suspect this happens because the requirement is not anymore visible in
the backlog so as it is the parent, it is just sorted at the bottom.
I'll note that down but as no one else complained about that behavior so
far I think it's not high priority for us.
fs
--
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
Agilo Software GmbH <http://www.agiloforscrum.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