It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×11,927
×5,826

question asked: Mar 12 '19, 2:27 p.m.
question was seen: 892 times
last updated: Mar 13 '19, 1:54 p.m.

Related questions

FAQ - How this Forum works

Can a stream in DOORS-NG be made read-only

0
Richard Hall (107●2●11) | asked Mar 12 '19, 2:27 p.m.

 Can a stream in DOORS-NG be easily made read-only?


It is possible that I might need to re-activate 'write-access' later, therefore a solution which allows me to re-enable with same permissions as it currently has would be ideal

Accepted answer

0
permanent link
Kathryn Fryer (503●1●4●7) | answered Mar 13 '19, 11:57 a.m.
You can't set permissions on a stream-by-stream basis; they apply to all streams.
You can create a baseline of the stream, which of course would be read-only. That wouldn't affect the stream itself.

Assuming you are using configuration management, you could mandate that the stream requires change sets linked to an approved work item for delivery. That would minimize users changing artifacts in the stream accidentally. You can restrict users' ability to create and deliver change sets as well, but that applies to all streams, so might not be appropriate.

Hope that helps.

Richard Hall selected this answer as the correct answer
Comments
Richard Hall commented Mar 13 '19, 1:54 p.m.

Thanks


This works well for me.

I changed the stream to require changes to be made in a Change Set (this prevents accidental editing)

I then required that the change set be linked to an approved change request or work item in order to be delivered.  Since we are not using approved change requests or work items, this stops anyone from delivering the changes.

To re-enable editing all that I need to do is to change those settings.

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.