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

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

Questions
Tags
Users
Badges
Matt UK
(6●1●1) 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.

0 votes

1 answer
3,579 views
0 votes

One answer

Permanent link
Geoffrey Clemm
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER (30.1k●3●30●35) Mar 29 '15, 11:02 a.m.
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.

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.

Ask a question
Guidelines
FAQ
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,020

Question asked: Jan 22 '15, 2:07 p.m.

Question was seen: 3,579 times

Last updated: Mar 29 '15, 11:02 a.m.

Confirmation Cancel Confirm