RRC: is it possible to show or hide the contents of a folder depending on the Team Area?
In RRC I can assign the ownership of a folder to a Team Area.
This way, only members of the Team Area can save artifacts in the folder and modify the artifacts contained in the folder.
Anyway, if a user is not member of the Team Area, he's still able to view the folder's contents, i.e. he has read access to the folder.
Is it possible to deny him this read permission, so that the visibility of artifacts is limited to members of the Team Area which created them?
Our RRC version is 4.0.6
|
Accepted answer
Hi Luca,
Unfortunately, it is not possible to deny read access to certain items within a project area. It is part of the project area design to allow any member of a project area full read access, even to items contained within a team area to which the user does not belong. If you would like to restrict read access for certain users, I would suggest that you create a new "private" project area which these users are not a member of, and then you can use the ReqIF Import feature to transfer and/or synchronize artifacts across these project areas.
There is also an open RM plan item which should be applicable to this scenario, so you can add your voice to the discussion: Fine Grained READ Access Control [CLM] (60206)
Hope this helps,
Mike Jaworski
Luca Martinucci selected this answer as the correct answer
|
2 other answers
The concept at this point is that users that have access to the Project Area will be able to see all the requirements in that project.
If you need visibility-separation, you'd need to structure your project with several Project Areas and linked them.
Also, you may be interested in these enhancement requests.
https://jazz.net/jazz03/web/projects/Requirements%20Management#action=com.ibm.team.workitem.viewWorkItem&id=78447
https://jazz.net/jazz03/web/projects/Requirements%20Management#action=com.ibm.team.workitem.viewWorkItem&id=73564
|
ReqIF in Version 4.0.5 has so many bugs, it is not really useable. At least not for casual use like this.
Too many duplicated types and attributes. |
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.