RQM Multiple Timelines require Team Areas even if you only have one team?
Abe Batthish (86●4●6)
| asked Nov 04 '13, 10:05 a.m.
JAZZ DEVELOPER edited Nov 04 '13, 1:53 p.m. by Max Bridges (241●2●6)
From my understanding, in order to associate a Test plan to a secondary timeline, you need to enable timelines and team areas. The dilemma is that although we have multiple releases on the fly at any given time: both main development and maintenance. There is only one test team working on validating these releases. But it seems that RQM requires that multiple team areas be created, one per timeline, in order for a test plan to be associated with one of those secondary timelines. This results in us having to create fake teams in order to perform this association.
Is this a hard requirement? Or is there a way to associate a test plan with a secondary timeline with the need to create all these team areas? |
One answer
Hi, having multiple team areas doesn't really mean different teams, for example, you can have the developent and maintenance team areas and both of them can have the exact same team for both without problems. Answering your question, yes, you need to create a team area for each timeline you need.
|
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.