It's all about the answers!

Ask a question

Parent story shown as Done when state is In Progress


Mark Ingebretson (58515236) | asked May 20 '09, 9:58 a.m.
We have an iteration plan for a release backlog iteration with some user
stories in a Scrum-based process.

The children tasks of the first user story are Planned For a separate
iteration. The Planned For field of the parent story is set to the
backlog iteration. Two of six of the children tasks are complete. The
state of the parent user story is In Progress.

The state of the parent user story as displayed above the user story in
the backlog iteration plan is set to Done.

Is this because there is no work assigned in the release backlog
iteration itself? That's expected behavior? There's not a correlation
between the state of the story and its status above?

Mark Ingebretson

4 answers



permanent link
Mark Ingebretson (58515236) | answered May 22 '09, 8:07 a.m.
Mark Ingebretson wrote:
We have an iteration plan for a release backlog iteration with some user
stories in a Scrum-based process.

The children tasks of the first user story are Planned For a separate
iteration. The Planned For field of the parent story is set to the
backlog iteration. Two of six of the children tasks are complete. The
state of the parent user story is In Progress.

The state of the parent user story as displayed above the user story in
the backlog iteration plan is set to Done.

Is this because there is no work assigned in the release backlog
iteration itself? That's expected behavior? There's not a correlation
between the state of the story and its status above?

Mark Ingebretson

Bumping this one again. (I can't seem to see the original post on the
web, only with Thunderbird.)

permanent link
Johannes Rieken (1.2k1) | answered Jun 02 '09, 5:51 a.m.
Mark Ingebretson wrote:
We have an iteration plan for a release backlog iteration with some user
stories in a Scrum-based process.

The children tasks of the first user story are Planned For a separate
iteration. The Planned For field of the parent story is set to the
backlog iteration. Two of six of the children tasks are complete. The
state of the parent user story is In Progress.

The state of the parent user story as displayed above the user story in
the backlog iteration plan is set to Done.

Is this because there is no work assigned in the release backlog
iteration itself? That's expected behavior? There's not a correlation
between the state of the story and its status above?


Are you talking about the work item state or the progress bar. The work
item state is something the users sets, hence, there is no correlation
between the state of parent/child work items. The progress bar, which is
shown in the work item editor, computes the progress based on its
children. If this is your issue, a screen shot would help me
understanding this.

--
Cheers, Johannes
Agile Planning Team

permanent link
Eitan Shomrai (9154) | answered Jun 10 '10, 2:15 a.m.
Mark Ingebretson wrote:
We have an iteration plan for a release backlog iteration with some user
stories in a Scrum-based process.

The children tasks of the first user story are Planned For a separate
iteration. The Planned For field of the parent story is set to the
backlog iteration. Two of six of the children tasks are complete. The
state of the parent user story is In Progress.

The state of the parent user story as displayed above the user story in
the backlog iteration plan is set to Done.

Is this because there is no work assigned in the release backlog
iteration itself? That's expected behavior? There's not a correlation
between the state of the story and its status above?


Are you talking about the work item state or the progress bar. The work
item state is something the users sets, hence, there is no correlation
between the state of parent/child work items. The progress bar, which is
shown in the work item editor, computes the progress based on its
children. If this is your issue, a screen shot would help me
understanding this.

--
Cheers, Johannes
Agile Planning Team

So if I use the Scrum template and Tasks are the "childs" of a "parent" Story, is there a way to change the parent's state to Resolved automatically when the last child moves to Resolved?
Thanks,
Eitan

permanent link
Kim Soederhamn (1.5k34348) | answered Jun 10 '10, 9:49 a.m.
Mark Ingebretson wrote:
We have an iteration plan for a release backlog iteration with some user
stories in a Scrum-based process.

The children tasks of the first user story are Planned For a separate
iteration. The Planned For field of the parent story is set to the
backlog iteration. Two of six of the children tasks are complete. The
state of the parent user story is In Progress.

The state of the parent user story as displayed above the user story in
the backlog iteration plan is set to Done.

Is this because there is no work assigned in the release backlog
iteration itself? That's expected behavior? There's not a correlation
between the state of the story and its status above?


Are you talking about the work item state or the progress bar. The work
item state is something the users sets, hence, there is no correlation
between the state of parent/child work items. The progress bar, which is
shown in the work item editor, computes the progress based on its
children. If this is your issue, a screen shot would help me
understanding this.

--
Cheers, Johannes
Agile Planning Team

So if I use the Scrum template and Tasks are the "childs" of a "parent" Story, is there a way to change the parent's state to Resolved automatically when the last child moves to Resolved?
Thanks,
Eitan

Not sure - but what you can do is set up the process template to require that all child tasks are closed before the parent can change status. Then this will not happen.

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.