Should one access changeset linked from a private workspace?
We have a interesting case about the permisson to access change set created in a private workspace.
A user created a private workspace and generated a couple of changeset which are linked to a work item. A teammate tried to view the changeset via the links in the work item. It works fine with RTC Eclipse client. But he got permission error while trying it via RTC web client: "Error fetching change set: User 'XXX' does not have permission to read workspace 'MMI Main Workspace' - Error code 403 The question is which is the expected behaviour? IS there a bug here? |
2 answers
Ralph Schoon (63.1k●3●36●46)
| answered Mar 13 '12, 12:34 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi,
I believe and have experienced other users should have no access to change sets that are in a private repository workspace. E.g. you can not run a private build from a private workspace since the build user has no access. In scoped repository workspaces it would depend on the role and membership of the user that treis. Public workspaces should be visible o all users (within the scope of the projects read permission). If the changeset is already delivered the scope of the stream should control who can see it. If you can verify and feel a workitem is in order, please submit one. |
https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/178560
Refer to that work item for more information. Basically, you should be able to see it because change sets aren't restricted even though the workspace is. |
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.