Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

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:
 
Main Development
                Release 1.0
                                Inception
                                Elaboration
                                Construction
                                Transition
 
I know that I can create a Release 2.0 with  the same categories underneath.
 
If I do create a Release 2.0:
 
Do I need to specify new identifiers even if I am using the same names?
If I have to specify new identifiers can I use the same names?
Will the “planned for”  drop down in the work item contain both Release 1.0 and 2.0
If I can’t use the same names using scenario defined above, is there any scenario I could use (i.e. blow away old time line and create new one)?
What if any ramifications would there be if I did?

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.

0 votes


Accepted answer

Permanent link
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

0 votes


One other answer

Permanent link
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.



0 votes

Your answer

Register or log in to post 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.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 12,024

Question asked: Nov 19 '14, 1:36 p.m.

Question was seen: 2,827 times

Last updated: Nov 24 '14, 4:24 a.m.

Confirmation Cancel Confirm