New iterations in a milestone carry over existing work items
When working with Iteration Plans in a milestone, I expected that when I create a new iteration, and clicked on Planned Items, that there would be no current Planned Items since I just created the iteration. However, it seems that all existing Work Items from the milestone are carried over into the iteration plan. I would like clarification as to why this is the behavior, and why the new iteration contains all tasks from previous iterations in under that Milestone.
Also, when I add a new Work Item to an iteration, why is that Work Item added to all other Iterations under that milestone? Maybe this is all part of the agile process, so Im hoping this post will get me (and hopefully others) the clarification that we need. Thanks, Jim Perry |
3 answers
Hi Jim,
the planned items page of an iteration plan is a query on the work items. So if you create a plan for team X / iteration M5, all work items assigned to members of that team X for iteration M5 show up on the plan. This has the nice behavior that changes to the planned items are reflected in work items and vice versa (no double capturing of the same information). However a M5 plan should only show work items that are planned for M5 and not for other iterations with the exception of parent work items. If you have a work item on the plan which has a parent work item which is assigned to a different iteration the parent work item shows up to complete the hierarchy. So if you see other work items on the plan this is a bug and I would like to ask you to file a work item against the Agile Planning component best with steps to reproduce. Dirk Agile Planning Component JPibm wrote: When working with Iteration Plans in a milestone, I expected that when |
|
Thanks Dirk,
That make sense. One follow up question: I believe most of my confusion stemmed from the following scenario: I have M2, which is made up of 3 iteration plans (Eclipse UI Testing, Eclipse Web UI implementation, Eclipse Web UI testing). When creating these iteration plans, I did not want work items from Eclipse UI testing to show up in the iteration plan for either Eclipse Web UI implementation, or Eclipse Web UI Testing. This did not make sense to me that each iteration plan in the milestone always has the same work items. Also, if I add a Work Item to Eclipse UI testing, it also gets added to the other 2 iteration plans, even though the Work Item is not associated to the other two iteration plans. Maybe I do not fully understand the concept of an iteration plan. Does what Im saying above make sense? Could you please clarify this for me? Thanks a bunch! - Jim |
Hi Jim,
An iteration plan is always scoped to an iteration and a team area. A team area on the other hand is associated to multiple work item categories. If you want the work items to show up in only one iteration plan, you have to create the appropriate team areas and make sure that the categories are assigned to them accordingly. Hopefully this answers you question. Cheers, Mike Jazz Agile Planning Team JPibm wrote: Thanks Dirk, |
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.