What are the restrictions when creating a time line in RTC 3.0
We are using RTC 3.0 and I am in the process of creating a time line. Our team does operations and maintenance for our system. I am trying to come up with a good scenario for O&M development and while trying came up with the following questions:
If I look at the default schedule for OpenUP it is something like this:
Like I said I am trying to come up with a good scenario for O&M development. Other than answers to the above questions if anybody has any suggestions I am more than willing to listen. |
Accepted answer
Ralph Schoon (63.7k●3●36●48)
| answered Nov 24 '14, 4:24 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I would suggest to follow Geoff's hint. In addition, come up with a good naming schema e.g
timeline Release 1 M1 [R1] M2 [R1] M3 [R1] M4 [R1] Release 2 M1 [R2] M2 [R2] M3 [R2] M4 [R2] Iterations that should be selectable in the planned for, require to select the "A release is planned for...." check box. In addition, you should make sure the times in the leaf iterations don't overlap. Bob Ferguson selected this answer as the correct answer
|
One other answer
Geoffrey Clemm (30.1k●3●30●35)
| answered Nov 22 '14, 11:43 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Every iteration in a given project area must have a distinct ID, but two iterations in the project area can have the same name.
The content in the Planned-For drop down had some limitations in early RTC releases, but in 5.0.1, you should be able to select any of the iterations in the Planned-For drop down. |
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.