Using current iteration with sub iterations
Our project has several working teams as part of our release. Some of those teams are using a 4 week iteration and some of the teams are using 2 week iterations. In order to make this work in RTC created a 4 week iteration (iteration 1) and two iterations of two weeks in length as children of the 4 week iteration (called 1a and 1b). The Timeline looks like this in the project area
Project timeline
>>Release 1.0.1
>>>>Iteration 1
>>>>>>Iteration 1a
>>>>>>Iteration 2b
Iteration 1a is set as the current iteration, which causes Iteration 1 and Release 1.0.1 to all have the current iteration marker.
In many of the queries, including the built it "Stories in current sprint" it only shows content that has a planned for setting of Iteration 1a.
Is there a way to get both "Iteration 1a" and "Iteration 1" the "current iteration" so that queries show content from both?
Project timeline
>>Release 1.0.1
>>>>Iteration 1
>>>>>>Iteration 1a
>>>>>>Iteration 2b
Iteration 1a is set as the current iteration, which causes Iteration 1 and Release 1.0.1 to all have the current iteration marker.
In many of the queries, including the built it "Stories in current sprint" it only shows content that has a planned for setting of Iteration 1a.
Is there a way to get both "Iteration 1a" and "Iteration 1" the "current iteration" so that queries show content from both?
2 answers
Our project has several working teams as part of our release. Some of
those teams are using a 4 week iteration and some of the teams are
using 2 week iterations. In order to make this work in RTC created a
4 week iteration (iteration 1) and two iterations of two weeks in
length as children of the 4 week iteration (called 1a and 1b). The
Timeline looks like this in the project area
Project timeline
Release 1.0.1
Iteration 1
Iteration 1a
Iteration 2b
Iteration 1a is set as the current iteration, which causes Iteration 1
and Release 1.0.1 to all have the current iteration marker.
In many of the queries, including the built it "Stories in
current sprint" it only shows content that has a target of
Iteration 1a.
Is there a way to both "iteration 1a" and "iteration
1" the "current iteration" so that queries show
content from both?
There is only one current iteration per timeline.
Queries for the current iteration can either refer to this iteration alone
('is') or the current iteration and its children ('is part of'), but there
is no option to express 'current iteration and its parent iteration'.
You could create a query for "iteration is '1' or iteration is '1a'", but
that query would have to be modified whenever the current iteration
changes.
--
Regards,
Patrick
Jazz Work Item Team
I've submitted work item 99946 ("Would like a query term for the current
iteration and all its parent iterations, recursively") for this.
Cheers,
Geoff
Patrick Streule wrote:
iteration and all its parent iterations, recursively") for this.
Cheers,
Geoff
Patrick Streule wrote:
Our project has several working teams as part of our release. Some of
those teams are using a 4 week iteration and some of the teams are
using 2 week iterations. In order to make this work in RTC created a
4 week iteration (iteration 1) and two iterations of two weeks in
length as children of the 4 week iteration (called 1a and 1b). The
Timeline looks like this in the project area
Project timeline
Release 1.0.1
Iteration 1
Iteration 1a
Iteration 2b
Iteration 1a is set as the current iteration, which causes Iteration 1
and Release 1.0.1 to all have the current iteration marker.
In many of the queries, including the built it "Stories in
current sprint" it only shows content that has a target of
Iteration 1a.
Is there a way to both "iteration 1a" and "iteration
1" the "current iteration" so that queries show
content from both?
There is only one current iteration per timeline.
Queries for the current iteration can either refer to this iteration
alone ('is') or the current iteration and its children ('is part of'),
but there is no option to express 'current iteration and its parent
iteration'.
You could create a query for "iteration is '1' or iteration is '1a'",
but that query would have to be modified whenever the current iteration
changes.