How to lock the actual state of a module in DoorsNG?
Thomas Fässler (11●1●1)
| asked Oct 29 '15, 8:16 a.m.
retagged Dec 21 '18, 4:49 a.m. by Minakshi Jaint (511●3) Hi,
Hope somebody could help us.
We have a big problem with Doors NG and we're thinking about rejecting it.
Because...
We did not find a way to lock a module respectively the actual state of it. So it happens that for example the RE is working on a SRS and another Developer just wants to read the SRS and accidentially edit an artefact. That is extremely dangerous, because the RE won't notice the change.
Thanks for any advice!
|
2 answers
Hello Thomas, In DNG, you can lock a module in DNG, however even if the module is locked, you may still be able to modify the artifacts in the module or a collection. Below is the link to locking modules: I was able to find a similar RFE against module locking: |
Hi Thomas,
I am sure IBM would not want me to recommend ditching DNG on their own forum, so I will try to suggest other avenues to work around the problem you describe. (Which leaves ∞-1 problems)
Given the scenario you write, maybe you should be using roles and permissions rather than locking. (If you need to allow developers to change artifacts in a module, this could be anything between painful and impossible.)
Another approach would be to require anyone who does not explicitly need to edit requirements to use only baselines for their work: then they could not inadvertently change anything. (And, of course, with Global Configuration, you could designate different streams.) This still requires care on the side of the user, so that they do not accidentally use the current version, or the wrong stream.
|
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.