Multiple Planned for value for a single Work Item RTC
Hello,
I query Work Items using the "Planned For" attribute for reporting. Recently, I have multiple components and it happens I accept change sets from an other component in order to reuse work, but this action have 2 cases:
- If the accepted change set doesn't create a conflict, then the change set is directly accepted.
- If the accepted change set create a conflict, then you must merge and create a new Work Item to relate your merge to.
The thing is, my other components can have a different iteration than the orignal component (of course the Work Item can be old enough to be in a different iteration), and when I query my Work Items using the "Planned For" attribute, the accepted change sets with no new Work Item are not displayed.
This is logic, but I would like to have the Work Items with the change sets used in different component, displayed in both queries (old and new one) for my reports.
Do you know if you can set multiple values to the attribute "Planned For" or if you have a workaround other than using tags ?
Thanks a lot.
2 answers
Planned for is heavily integrated into the UI with various capabilities.
You can add a custom attribute of type iteration, but that would have no integration with anything.
I also need to mention that it does not make any sense to do it this way. One work item is one work item. And one work item can have only one owner, can only be planned for one iteration.
If you want your process make sense, I would suggest to create another work item if the change set or part of the work must be planned for another iteration.
The semantics of PlannedFor is "the iteration in which the change sets for this work item will be created". This is important because the estimated cost of creating those change sets (a property of the work item) will then be assigned to that iteration, and the FiledAgainst property will indicate which team will be doing the work.
It appears that for your report you want "work items whose changes will be added in this iteration". For that report, you cannot used PlannedFor ... you could either use tags, or create your own multi-valued iteration property. But note that this report would not tell you which team is supposed to be doing the work ... unless you are assuming that the same team that created the change sets would be delivering the change sets to the other streams.
To provide more guidance, you would need to explain what exactly is the purpose of this report (e.g., how it will be used by your development teams).
Comments
