iteration hierarchy and planned for field
Since I can create a hierarchy of iterations, why does the 'planned for' field in the work item just show a simple iteration name instead of an iteration path? If I were to create two iterations with the same name, then they would both appear in the 'planned for' field with their simple name and you couldn't distinguish one from another. Is this a bug or is this deliberate?
Just trying to get a better understanding. Lorelei |
2 answers
Iterations have an identifier and a name. Identifiers are used inside
the process specification to refer to iterations. The names are used in the UI such as the work item editor. The UI doesn't usually show iteration paths as they can get long pretty quickly. Long paths are not too useful in the UI. E.g., either the drop downs in the work item editor would need to be rather wide or the user user would have to scroll horizontally to see the full path. Iteration names can be changed without invalidating the process specification, the iteration hierarchy, or anything else. Thus, when you have a situation in which two names are the same you can easily change one of them. Kai Jazz Process Team lngooi wrote: Since I can create a hierarchy of iterations, why does the 'planned |
Kai,
Thanks for you reply. So then the recommendation would be to make sure that iteration names are unique to avoid user confusion. Lorelei |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.