Current iteration
I'm using the "Require Work Item and Comments" preconditon with "Iteration work item is planned for" = "must be current iteration" with multi timeline/teams but getting unexpected results.
During delivery, what is RTC using for "current iteration"? Is it using the current iteration of the team that owns the stream or is it using the team that owns the work item? |
3 answers
Geoffrey Clemm (30.1k●3●30●35)
| answered Jan 03 '12, 10:23 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
The operation (deliver) is being applied to a stream, so it is the team
area that owns the stream whose current iteration is what matters. So that means that if you set "delivery must be for current iteration", then you can only deliver work items that are in a project area with the same timeline as team area that owns the stream. Just for interest's sake, why do you have the work items in one team area, but the stream in a different team area? Cheers, Geoff On 1/3/2012 10:08 AM, eanderso wrote: I'm using the "Require Work Item and Comments" preconditon |
|
I have 2 streams, a development and a release stream. Once an iteration we seed the release stream with baselines from the development stream and use the release stream to harden the iteration (i.e. iteration n). This free's the development stream to move on to the next iteration (i.e. iteration n+1).
I setup a Development Stream owned by Development Team working on Development timeline and a Release Stream owned by Release Team working on Release timeline. I want to make sure that deliveries to the release stream have work items that are associated with the current iteration of the release timeline AND deliveries to the development stream have work items that are associated with the current iteration of the development timeline. I was testing that a delivery to the release stream had a work item planned for the current iteration of the release timeline. However, I found I could deliver if the work item was planned for the current iteration of the development timeline too. Also, in a test where I used a non-current iteration in the planned for, the team advisor correctly stopped the deliver but the quick fix changed the planned for to the current iteration of the development timeline. |
|
Geoffrey Clemm (30.1k●3●30●35)
| answered Jan 05 '12, 9:08 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I've submitted defect 190263 for allowing delivery to the wrong current
iteration. I've submitted defect 190266 for the current iteration quick fix selecting the wrong current iteration. Thanks for reporting them! Cheers, Geoff On 1/5/2012 3:53 PM, eanderso wrote: I have 2 streams, a development and a release stream. Once an |
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.