It's all about the answers!

Ask a question

ERM (RRC): is it possible to move requirements to another project area

Erich Lagler (1) | asked Oct 16 '23, 7:28 a.m.

We need to move some requirements to another project area. No copy should be created here so that the single point off truth is maintained. Because it is necessary for a subproject to move some requirements that those involved can only see relevant requirements.

2 answers

permanent link
Bhagath P B (3887) | answered Oct 16 '23, 7:40 a.m.

 Hi Erich,

If your project is enabled with configuration management, then you can Clone from Component.

Erich Lagler commented Oct 16 '23, 9:02 a.m. | edited Oct 16 '23, 11:53 a.m.

Hi Bhagath P B,

we have configuration management not enabled, and in this case it wouldn't be a solution to the problem.
In ERM we cannot limit the reading rights, so we have to move requirements, not clone or copy - a single point off truth is to be maintained.

permanent link
Davyd Norris (2.1k217) | answered Oct 16 '23, 7:53 p.m.
You can't move requirements between project areas, you can only copy and then delete from the original. Unfortunately this will create new DNG IDs for them.

Bear in mind that the deleted requirements are only soft deleted and will still be visible in any baselines you have created. It is possible to hard delete requirements but it's a more involved process

Your answer

Register or to post your answer.