RQMv4.0.2 Retire vs Lock
Currently the retired behaves like locked in such a way that a retired test case can be linked to a test plan and a TCER can be generated and executed. Isn't it retired? It will not surpprise me if this happens to a locked.
But by 'retired' I expect that the test case should not appear in the search result if not specified purposely, and it should not be allowed for new TCERs/execution unless it is unretired.
Am I understanding it properly?
Accepted answer
Comments
Good about the restore function.
I believe once deleted they are not showing up in any reports or queries. If still want to run reports/queries, we need to restore back, and restore back everything. Or can we report/query in the trash view? Can we do audit in the trash view (timestamps and etc. are well kept)?
Correct, deleted artifacts cannot be included in table views, reports, etc. However, you can still open the deleted artifact in the editor for read-only viewing. As such, you can audit deleted artifacts.
That is great and I hope it is convenient to do so.
Another concern is that we might load and delete a lot of wrong stuff, and they should be deleted permanently. But it sounds like there no way to permanently delete. Then after a few years, the trash view becomes very big with both 'retired' and permanently 'deleted' stuff, that might make it so hard to use. Is this concern valid?
You can permanently delete artifacts in the Trash view. Note, the scalability of the Trash view is not an issue.
Thanks Paul, I am going back to our management team and tell them this and recommend we upgrade to 4.0.5, at least we install one and see how it works.