It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×11,968
×3,952
×30
×3
×1

question asked: Jan 22 '15, 2:07 p.m.
question was seen: 3,240 times
last updated: Mar 29 '15, 11:02 a.m.

Related questions

How to best plan for Modifying Requirements in RRC Across Multiple Releases

0
Matt UK (6●1●1) | asked Jan 22 '15, 2:07 p.m.
 What is best practice for editing/modifying existing requirements if a requirement is being referenced in multiple releases?

I am debating on Making the 'release #' a custom attribute and filtering on that or creating the modified requirement as a new requirement and linking the 2 requirements (Old/New) together and associating them to different releases. Ultimately the goal is to be able to run reports on all 'in scope' requirements on a given release  (ie. 2 or 3)-- if i just change the requirement it will have a different meaning for a Release 2 report or a Release 3 Report.

One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Geoffrey Clemm (30.1k●3●30●35) | answered Mar 29 '15, 11:02 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Your best approach is to use DNG-6.0, where versioning and configuration management is supported.   You can then have a separate configuration for Release-1 and Release-2, and then have different versions of that requirement selected in those two configurations.

Your answer

Register or 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.