Current iteration check box in query
Hi, the meaning of the 'current iteration' checkbox in the query builder
is to mean only the iteration marked as current. We have some teams
working on 2 week iterations and some on 4 week iterations. The ones
working on 4 week iterations use an iteration which is the parent of the
current 2 week iteration. But this means (from the query builder
perspective) that only the 2 week iteration is current. This causes
problems for people working to 4 week iterations using the 'current
iteration' flag on the query builder.
e.g. team 1 works to 4 week iteration, team 2 works to 2 week iterations
(the end dates of the 4 week iterations are the same as the end date of
every-other 2 week iteration). Iteration I1 has two child iterations I1A
and I1B. Team 1 creates iteration plans from I1, I2, I3 etc. Team 2
creates iteration plans from I1A, I1B, I2A, I2B etc.
If we make I1A the current iteration, team 2 is happy as the work
they're planning in their I1A iteration plan can be found via a query
for work items in 'current iteration'. However, team 1 is not happy as
they are working on a plan for I1 and since I1A is the current iteration
and not I1 they are not working on the current iteration and can't find
their work items through a query on 'current iteration'. Setting the
current iteration to I1 has a similar problem.
Does anyone have any advice here? Perhaps I should open an enhancement
for a check-box on the 'planned for' condition 'current and parent
iterations'?
Thanks,
Jeremy
is to mean only the iteration marked as current. We have some teams
working on 2 week iterations and some on 4 week iterations. The ones
working on 4 week iterations use an iteration which is the parent of the
current 2 week iteration. But this means (from the query builder
perspective) that only the 2 week iteration is current. This causes
problems for people working to 4 week iterations using the 'current
iteration' flag on the query builder.
e.g. team 1 works to 4 week iteration, team 2 works to 2 week iterations
(the end dates of the 4 week iterations are the same as the end date of
every-other 2 week iteration). Iteration I1 has two child iterations I1A
and I1B. Team 1 creates iteration plans from I1, I2, I3 etc. Team 2
creates iteration plans from I1A, I1B, I2A, I2B etc.
If we make I1A the current iteration, team 2 is happy as the work
they're planning in their I1A iteration plan can be found via a query
for work items in 'current iteration'. However, team 1 is not happy as
they are working on a plan for I1 and since I1A is the current iteration
and not I1 they are not working on the current iteration and can't find
their work items through a query on 'current iteration'. Setting the
current iteration to I1 has a similar problem.
Does anyone have any advice here? Perhaps I should open an enhancement
for a check-box on the 'planned for' condition 'current and parent
iterations'?
Thanks,
Jeremy
2 answers
Does anyone have any advice here? Perhaps I should open an enhancement
for a check-box on the 'planned for' condition 'current and parent
iterations'?
The Current Iteration variable is actually a 'Current Iterations' variable
(it includes all iterations marked as 'current').
So if the teams would work on iterations in different timelines, both
would see the right work items.
This doesn't solve your problem, though, and I think a request for a
'current iteration and its parent chain' variable certainly makes sense.
--
Regards,
Patrick
Jazz Work Item Team
On 15/09/2009 10:52, Patrick Streule wrote:
http://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=94516
Jeremy
Does anyone have any advice here? Perhaps I should open an enhancement
for a check-box on the 'planned for' condition 'current and parent
iterations'?
The Current Iteration variable is actually a 'Current Iterations'
variable (it includes all iterations marked as 'current').
So if the teams would work on iterations in different timelines, both
would see the right work items.
This doesn't solve your problem, though, and I think a request for a
'current iteration and its parent chain' variable certainly makes sense.
Thanks. I've opened WI 94516:
http://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=94516
Jeremy