Issue Details (XML | Word | Printable)

Key: JRA-12335
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Sam Chang [Atlassian]
Reporter: Donna McGahan [Atlassian]
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
JIRA

Project Role Modifications not reflected in Issue Security Scheme

Created: 07/Mar/07 03:02 PM   Updated: 08/Mar/07 07:48 PM
Component/s: Roles, Security
Affects Version/s: 3.7.4
Fix Version/s: 3.8.1

Time Tracking:
Not Specified

Participants: Anton Mazkovoi [Atlassian], Donna McGahan [Atlassian] and Sam Chang [Atlassian]
Since last comment: 1 year, 31 weeks, 2 days ago
Resolution Date: 08/Mar/07 07:48 PM
Labels:


 Description  « Hide
If you modify users/groups in a project's project role and this project uses an issue security scheme, you must remove the role and re-add it to the issue security scheme for the role changes to take effect.

Steps to Reproduce:
1. Need to be the admin of a project whose issue creation screen has the security level field and of which you have permission to set issue security level.
2. Create Issue Security Scheme with two levels (Level A and Level B).
3. Add the Administrator role to Level A and the User role to Level B.
4. Assign the Issue Security Scheme to your project.
5. Add yourself to Project A's Administrator Role.
6. Look at the options available under Security Level. You will only see None.

Even though you've added yourself to the Administrator role, you won't have the ability to set the issue security to Level A unless you delete and re-add the Administrator role to the Level A security level.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Sam Chang [Atlassian] added a comment - 08/Mar/07 07:47 PM
The cache has been flushed for deleting project roles and adding/removing user/group to roles