Key: |
QB-979
|
Type: |
Bug
|
Status: |
Resolved
|
Resolution: |
Fixed
|
Priority: |
Major
|
Assignee: |
Unassigned
|
Reporter: |
Karim Heredia
|
Votes: |
0
|
Watchers: |
0
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 07/Jul/11 10:50 AM
Updated: 23/Jul/11 03:03 AM
|
|
Component/s: |
None
|
Affects Version/s: |
3.1.48
|
Fix Version/s: |
3.1.53
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
Environment:
|
Linux 64-bit
|
|
We are planning to open workspace access to owners of configurations, but we don't want them to see other workspaces.
We ran the following test:
1. Created configurations like this:
Root
| -------> Config A
| -------> Config B
2. A user was configured so he could see only build logs at the Root level and can see Config A's workspace.
3. User clicks on Root from Configurations tab. There is no workspace link (correct).
4. User clicks on Config A from Configurations tab. There is a workspace link pointing to Config A's workspace (correct).
5. If user clicks on the Root link at the top of the page while the Config A workspace is open, the user can see the Root workspace and therefore also Config B's workspace (incorrect).
|
Description
|
We are planning to open workspace access to owners of configurations, but we don't want them to see other workspaces.
We ran the following test:
1. Created configurations like this:
Root
| -------> Config A
| -------> Config B
2. A user was configured so he could see only build logs at the Root level and can see Config A's workspace.
3. User clicks on Root from Configurations tab. There is no workspace link (correct).
4. User clicks on Config A from Configurations tab. There is a workspace link pointing to Config A's workspace (correct).
5. If user clicks on the Root link at the top of the page while the Config A workspace is open, the user can see the Root workspace and therefore also Config B's workspace (incorrect).
|
Show » |
There are no comments yet on this issue.
|
|