"Planned For" in Work Item ?
I created iteration "M1" and a plan under it - "M1 Plan". So I have a iteration and a plan for it.
Now, I created a work item and selected the "Planned for". I could only see the M1 in the list and no "M1 Plan" in the list. WHY?
Since it is "Planned for", I think I should select the iteration plan which is M1 Plan.
Am I right?
Or work item can only plan for iteration rather than iteration plan?
Now, I created a work item and selected the "Planned for". I could only see the M1 in the list and no "M1 Plan" in the list. WHY?
Since it is "Planned for", I think I should select the iteration plan which is M1 Plan.
Am I right?
Or work item can only plan for iteration rather than iteration plan?
4 answers
Hello cheval,
To be able to plan for an iteration i believe the iteration needs the check
box "A release is scheduled for this iteration" to be checked.
Rationale behing this is you could have finer grained iteration structures
underneath an iteration that are used for process behavior specification
rather than for planning.
Ralph
To be able to plan for an iteration i believe the iteration needs the check
box "A release is scheduled for this iteration" to be checked.
Rationale behing this is you could have finer grained iteration structures
underneath an iteration that are used for process behavior specification
rather than for planning.
Ralph
I created iteration "M1" and a plan under it - "M1 Plan". So I have a
iteration and a plan for it.
Now, I created a work item and selected the "Planned for". I could
only see the M1 in the list and no "M1 Plan" in the list. WHY?
Since it is "Planned for", I think I should select the iteration plan
which is M1 Plan.
Am I right?
Or work item can only plan for iteration rather than iteration plan?
You are correct that the Planned For value can only be set to a release or iteration. The choice of a particular iteration plan is made by whichever team area the work item is assigned to. This is usually driven by your choice of 'Filed Against'.
So, for example, say that Team A is associated to Category A. You create Task Z and set the 'Planned For' to M1, and the 'Filed Against' to 'Category A'. The 'Filed Against' setting will dictate which team the work item is assigned to, and if that team has an iteration plan for iteration M1, then it will appear within that iteration plan.
Hope that helps.
Kieron
So, for example, say that Team A is associated to Category A. You create Task Z and set the 'Planned For' to M1, and the 'Filed Against' to 'Category A'. The 'Filed Against' setting will dictate which team the work item is assigned to, and if that team has an iteration plan for iteration M1, then it will appear within that iteration plan.
Hope that helps.
Kieron
Hi, rschoon,
For what you said that "Rationale behing this is you could have finer grained iteration structures underneath an iteration that are used for process behavior specification rather than for planning. "
I tried to input "Planned for " with different iterations, say M1 for work item A and M2 for work item B. And I changed the permission of M1 and M2, say in M1, people can modify the owner of work item and M2 can not allow the modification.
However, no matter which iterations a work item planned for, it just follows the current iteration process. If the current iteration is M1, all work items can change the owner. If the current iteration is M2, all work items cannot even those planned for M1.
Would you please advise further?
For what you said that "Rationale behing this is you could have finer grained iteration structures underneath an iteration that are used for process behavior specification rather than for planning. "
I tried to input "Planned for " with different iterations, say M1 for work item A and M2 for work item B. And I changed the permission of M1 and M2, say in M1, people can modify the owner of work item and M2 can not allow the modification.
However, no matter which iterations a work item planned for, it just follows the current iteration process. If the current iteration is M1, all work items can change the owner. If the current iteration is M2, all work items cannot even those planned for M1.
Would you please advise further?