Preventing Workspace Creation in Specific Streams
Is there any way to prevent specific users (or roles or teams) from creating a repository workspace off of a specific stream? I have three streams: Integration, QA, and Production. I wish to keep the developers' team from being able to do anything with the QA or Production streams, but can't figure out how.
I have created developer and QA teams, assigned users to them, and set the ownership of the streams to the appropriate team. (QA team owns QA and Production, developer team owns Integ.) Even so, someone from the developer team can create a repository workspace off the QA stream. How do I fix this? |
5 answers
Not today. There are currently no mechanisms to limit which baselines or which components users can add to their workspaces.
Cheers, Jean-Michel |
Geoffrey Clemm (30.1k●3●30●35)
| answered Oct 01 '09, 12:03 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
To prevent developers from doing anything to the QA or production
streams, just prevent them from writing to those streams (see http://jazz.net/library/article/215#protect_some). Or are you concerned that they will by mistake create a workspace based on that stream, and make some changes, only to discover that they can't deliver those changes? Note that in this case, they can re-target their workspace to the right stream ... but they might need to do some merging before they can deliver their changes. Cheers, Geoff tmckemy wrote: Is there any way to prevent specific users (or roles or teams) from |
Is there any way to prevent specific users (or roles or teams) from creating a repository workspace off of a specific stream? I have three streams: Integration, QA, and Production. I wish to keep the developers' team from being able to do anything with the QA or Production streams, but can't figure out how. You can try simpy change the owner of specific stream, and other users which are not team members of new owner of specific stream will not have possibility to write to that stream! |
|
Thanks to all of the respondents.
I solved my problem by placing the "Restrict change set delivery to components in a stream" pre-condition on the "Source Control => Deliver (Server)" operation for each of the teams. You can select who has permission to deliver to a particular component in a particular stream, and it works quite well. The downside is you can't do this in the process template since the teams, streams, and components muct exist prior to applying this precondition. (Thanks to Harry Koehnemann at Rocket Gang for some outside help as well.) |
Hello,
I have tried implementing this in both RTC 2.0.0.2 and 3.0 and am seeing the same behavior. Using the "Restrict Change set delivery to components in a stream" preconditon set for the "Deliver(server)" operation for the TeamMember role. I can set the permission on a single component in a stream to a role(ie.Product owner), however, when I choose an additional/different stream(different or same component) and set the same permissions/role and then Save the Team Area, it only saves one of the Streams/component permissions that I have changed. Basically, the UI allows you to save one stream setting but not both. Also, when switching the stream drop down, the grid does not reflect the changes saved in the process config. Has anyone reported this before? Why are we limited to only 1 stream Cheers, Patrick Gagan |
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.