Loading Profile...
How to handle story dependencies in Tracker?
Building a project from scratch in Tracker? How would we build stories without dependency's? I am not sure how to do it, seems like if I am building a user area, I need to build separately the authentication, registration, but both of those are part of a bigger story. Can you kindly help with what a suggested methodology for this.
I’m unsure
3
people have this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
-
Inappropriate?The way I do dependencies is to order the stories in such a way that dependencies are completed before the story I'm looking at.
Since you can't build authorization before you have authentication, you would put authentication before authorization.
Also, the iteration itself might be the "bigger story": a single iteration for authn / authz. -
Inappropriate?another organic way to indicate dependencies would be to use comments that contains a permalink to the other story. the permalink is displayed at the bottom of the story detail view. -
Inappropriate?Do you think it would add value to the product to be able to define dependencies and have them displayed as a report? For instance: I have a project that has 4 tasks. One of the tasks does not have any dependencies. But the other three tasks have to be done in order. the one task takes 4 points, but the 3 tasks combined take 6 points. A graph showing these dependencies would make it really easy to identify the critical path of the project and really aid resource allocation.
What do you guys think? -
Inappropriate?The question ends up being the UI. How do you indicate dependencies. Drag and drop would be nice, but then how do you reorder?
Maybe there could be another type of item: master task. Features could then be added to "master tasks", indicating dependencies. Would that become cumbersome? We'd need some user testing.
