We have a organizational process that requires me to put our bugs through several states after the work to fix them is completed. We have a problem because as soon as the developers move the remaining time to fix the bug to 0, the bug is closed and the developer must reopen it, reassign it, and then set it's next status (ready for verification). Is there a configuration flag I can set to disable this behavior for bugs (we use it frequently for tasks so I'd like it to continue to work there)?
Thanks, Nathan Banek -- 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
