Uniqueness of iteration ID's and good naming conventions
Ralph Schoon (63.3k●3●36●46)
| asked Mar 04 '09, 6:11 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi,
I have been working with RTC for quite a while doing installations and demos. One thing that bugs me a little is that I can not seem to figure the reach of an iteration ID. Is it supposed to be unique within a development line or does it have to be unique over all development lines? Also, in case one has several (many) development lines is there some best practice or naming convention that proved to work good? Thanks, Ralph |
3 answers
Iteration IDs must be unique only among its peer iterations (within the same
parent). The parent is either a development line, or another iteration. The naming of development lines and iterations would be really specific to each project, or maybe guided by the process template being used. I don't have any more to offer in terms of best practice. --- Ryan Manwiller Jazz Team |
On 3/9/09 1:07 PM, Ryan Manwiller wrote:
Iteration IDs must be unique only among its peer iterations (within the Ryan, are spaces allowed in an iteration identifier? I can't find that in the documentation. |
On 3/9/09 1:07 PM, Ryan Manwiller wrote: Iteration IDs must be unique only among its peer iterations (within the Ryan, are spaces allowed in an iteration identifier? I can't find that in the documentation. Yes, spaces are allowed in the iteration identifier. |
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.