Completion time for stories with common dependencies
A great part of the RTC plan view is that story progress is calculated based on the child tasks. Story A's progress is calculated from child task 1 and task 2.
What if a task naturally belongs to two stories? Say Story B ought to also include task 1. I cannot set task 1 as a child of two stories. If I use blocks/depends-on, the relationship is preserved but the information is not reflected on Story B's time remaining.
What is the best way to represent the dependencies so that I get time remaining views for each story?
What if a task naturally belongs to two stories? Say Story B ought to also include task 1. I cannot set task 1 as a child of two stories. If I use blocks/depends-on, the relationship is preserved but the information is not reflected on Story B's time remaining.
What is the best way to represent the dependencies so that I get time remaining views for each story?
One answer
For this, you'll probably need the "predecessor" relationship defined in
the Formal Project Management template. You will then see the timing in
the Gant chart display, rather than the progress bar. Ideally, you'd be
able to just use the "predecessor" relationship in whatever template you
happened to pick/create, but currently, the most reliable way to get
that functionality is to work in a project area that was initialized by
the Formal Project Management template.
Cheers,
Geoff
On 1/11/2012 3:08 PM, afreed wrote:
the Formal Project Management template. You will then see the timing in
the Gant chart display, rather than the progress bar. Ideally, you'd be
able to just use the "predecessor" relationship in whatever template you
happened to pick/create, but currently, the most reliable way to get
that functionality is to work in a project area that was initialized by
the Formal Project Management template.
Cheers,
Geoff
On 1/11/2012 3:08 PM, afreed wrote:
A great part of the RTC plan view is that story progress is calculated
based on the child tasks. Story A's progress is calculated from child
task 1 and task 2.
What if a task naturally belongs to two stories? Say Story B ought to
also include task 1. I cannot set task 1 as a child of two stories.
If I use blocks/depends-on, the relationship is preserved but the
information is not reflected on Story B's time remaining.
What is the best way to represent the dependencies so that I get time
remaining views for each story?