Pinned topic ClearDDTS: How to provide access control on INDIVIDUAL bugs/records
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Within a DDTS project, can access control on INDIVIDUAL bugs/records be restricted to certain users?
Updated on 2007-12-17T20:24:27Z at 2007-12-17T20:24:27Z by SystemAdmin
SystemAdmin 110000D4XK280 Posts
Re: ClearDDTS: How to provide access control on INDIVIDUAL bugs/records2007-12-17T20:24:27ZThis is the accepted answer. This is the accepted answer.Yup. See chapter/section 12-10 (Security) in your admin guide.
(err, well my version is 4.7, your mileage may vary)
For modification priv., thats based on project/state/user permissions as normal.
For READ access, you have to
1) add a line 'Bug-read: Y' to your ~ddts/etc/ddtsrc file
(turns on per-defect read access control - this is mutually exclusive to project read access control)
2) each bug submitted now will have a Security-token field assigned; the value of this field will match the user's tokens defined in ~/etc/security