Timelines and Iterations
Looking for a recommendation on proper use of timelines and iterations.
We have a product, which has several releases active. Current, Future, and Past. I am guessing I would designate those as Timelines. Then for each of them I would create iterations only one of which would be the active one for that Timeline. For example, each one would contain an M1 milestone. Does that sound right? When I implement that above, and I assign a Work Item to an iteration, the dialog box for selecting iterations doesn't properly show the timeline hierarchy. Instead of showing Current -> M1 and Future -> M1 it shows two M1s which I can't differentiate. So, I am guessing I just need to disambiguate by name? Or am I thinking of this incorrectly? |
2 answers
Geoffrey Clemm (30.1k●3●30●35)
| answered Oct 22 '10, 11:44 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Yes, you need to disambiguate the names ... and "current" "future" and
"past" are obviously not good names for releases (:-). If you use integers like 1.0, 2.0, and 3.0, and then the iterations get obvious values, like "1.0 M1" and "2.0 M1". Cheers, Geoff On 10/21/2010 2:37 PM, ScottChapman wrote: Looking for a recommendation on proper use of timelines and |
Thanks Geoff. That's what I thought. "Past", "Current", and "Future" were just for illustration purposes.
-Scott. Yes, you need to disambiguate the names ... and "current" "future" and |
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.