Stories with real subtasks
Story tasks are nice. They could be improved further. It would be nice to actually have a group of tasks instead. So that it would have real subtasks that can be assigned to people (have all the things that normal tasks do).
This way a Story could have sub tasks that are for example part coding for the developer(s) and part that is making the graphics for that same feature on another person. One would then be able to see dependencies more clearly.
Sometimes some of the subtasks might be re-piroritized and then one should be able to move them out.
I ́d also like to see like a tree view for the subtasks of a Story.
This way a Story could have sub tasks that are for example part coding for the developer(s) and part that is making the graphics for that same feature on another person. One would then be able to see dependencies more clearly.
Sometimes some of the subtasks might be re-piroritized and then one should be able to move them out.
I ́d also like to see like a tree view for the subtasks of a Story.
4
people like this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
-
Inappropriate?Hi, thanks for the suggestion. We did consider making story tasks into things that behaved more like real stories, but decided it would introduce too much complexity, and compromise Tracker's lightweight nature and easy of use. As implemented, story tasks are basically just a more structured way to capture additional information about a given story, i.e. a work-in progress to-do list. In situations where you have a large feature, we recommend that you break it down to smaller stories, and use the labels feature to keep track of the fact that the stories are related.
-
Using labels might be tedious though..for tracking purposes. What do folks out here think>
Loading Profile...



EMPLOYEE