Hey Nathan, On Monday 07 June 2010, [email protected] wrote: > My primary need for subtasks is to break down bugs into smaller > chunks. I want to maintain fidelity with the bug as originally > written so we don't break them into multiple bugs. Rather I want > them broken into subtasks when they are big enough to require that > much work to resolve.
By default, you can also link a User Story to a Bug (creating a link chain: Bug -> Story -> Task). You would create your tasks (with remaining time) either directly on the bug (for lightweight bugs) or write a User Story that is necessary to implement in order to solve a bug. In any way, if you need to create a "group" of tasks, the tool currently requires you to rather leave tasks untouched (so no smaller "sub-tasks") but create a "super-task" above it. > I also occasionally use tasks to capture internal effort that is of > limited or no interest to our customer such as refactoring or > re-architecture efforts. I realize we could just write user stories > for these efforts against a software maintainer role, but I hadn't > taken time to set that up yet. Definitely! Tracking these in their own backlog of Impediments or Technical Stories allows you to better prioritize and pull them into a sprint. Robert -- 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
