It's all about the answers!

Ask a question

Obsolete Requirements & Test Cases


Paul George (122) | asked Jul 26 '11, 6:37 p.m.
I do not see any clean way to mark requirements as obsolete on the RQM side. Deleting wouldn't seem to have the right effect, since they still show up under View Requirements and are associated with past test plans.
We have a situation where a number of System Use Cases in Requisite Pro are being retired and replaced with another set. This makes a large number of our test cases obsolete as well. I do not want the old requirements to be visible or shown as not traced to test cases. I may just be confused on how things work. There is nothing in the documentation on the effect of the retired status for test cases or scripts, and requirements seem to only have statuses of

We are running 2.0.1.1 iFix 3

One answer



permanent link
Lei Shi (2271) | answered Jul 26 '11, 10:59 p.m.
Sync requirements will mark thoes requriements are removed and you can accept the change and then all thoes requirement will be archived and will nerver shown in RQM any more.

I do not see any clean way to mark requirements as obsolete on the RQM side. Deleting wouldn't seem to have the right effect, since they still show up under View Requirements and are associated with past test plans.
We have a situation where a number of System Use Cases in Requisite Pro are being retired and replaced with another set. This makes a large number of our test cases obsolete as well. I do not want the old requirements to be visible or shown as not traced to test cases. I may just be confused on how things work. There is nothing in the documentation on the effect of the retired status for test cases or scripts, and requirements seem to only have statuses of

We are running 2.0.1.1 iFix 3

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.