Queries and "current" iteration
RTC 2.0.0.0
I have timelines defined as follows:
Milestone 1
-> Iteration 1
--> Iteration 1a
--> Iteration 1b
If I create a query that uses "current iteration" and the current iteration is set to 1b should the query also return those work items targeted for Iteration 1 and Milestone 1? Looking in the Eclipse client all 3 (Milestone 1, Iteration 1, and Iteration 1b) have the icon indicating current iteration.
Thanks.
I have timelines defined as follows:
Milestone 1
-> Iteration 1
--> Iteration 1a
--> Iteration 1b
If I create a query that uses "current iteration" and the current iteration is set to 1b should the query also return those work items targeted for Iteration 1 and Milestone 1? Looking in the Eclipse client all 3 (Milestone 1, Iteration 1, and Iteration 1b) have the icon indicating current iteration.
Thanks.
4 answers
RTC 2.0.0.0
I have timelines defined as follows:
Milestone 1
-> Iteration 1
--> Iteration 1a
--> Iteration 1b
If I create a query that uses "current iteration" and the
current iteration is set to 1b should the query also return those
work items targeted for Iteration 1 and Milestone 1? Looking in the
Eclipse client all 3 (Milestone 1, Iteration 1, and Iteration 1b)
have the icon indicating current iteration.
The 'Current Iteration' variable would be better termed 'Current
Iterations'. It selects all current iterations. In order to limit the
query to only one timeline, you would need to add more conditions like
e.g. the Team Area.
There is a work item to make the 'Timeline' pseudo-attribute also queryable.
--
Regards,
Patrick
Jazz Work Item Team
Patrick, my apologies - I asked my question poorly. I wish to have (in my example) anything targeted for the higher level iterations returned as well. So if the current iteration is 1b I want to know if a query using "current iteration" will also return work items planned for Iteration 1 and Milestone 1. That does not seem to be the behavior I am seeing.
Thanks.
Thanks.
The "current iteration" query term only matches the specified iteration,
not its parent iterations.
Work item 99946 is an enhancement to support querying for the parent
iterations.
Please feel free to add a comment to that work item to indicate your
interest/support.
Cheers,
Geoff
klzemanek wrote:
not its parent iterations.
Work item 99946 is an enhancement to support querying for the parent
iterations.
Please feel free to add a comment to that work item to indicate your
interest/support.
Cheers,
Geoff
klzemanek wrote:
Patrick, my apologies - I asked my question poorly. I wish to have
(in my example) anything targeted for the higher level iterations
returned as well. So if the current iteration is 1b I want to know
if a query using "current iteration" will also return work
items planned for Iteration 1 and Milestone 1. That does not seem to
be the behavior I am seeing.
Thanks.
I can't seem to find work item 99946. Has it been removed without actioning? This is extremely useful to do as it helps prepare release notes for a PRODUCTION release (parent iteration) that comprises several UAT releases (child iterations). I need to be able to see work items per UAT release so I can tell my users what fixes they should expect in every UAT, but also be able to produce final release notes for the production release which is by definition a list of all items in the sub-UAT releases.
Thanks