Page History
...
Each user has one of the following access levels to a structurestructure010:
None | The user does not see the structure at all and does not know that it exists. |
View | The user can view the structure but cannot make changes. |
Edit | The user can view the structure and can rearrange issues in the structure, add issues to the structure and remove issues from the structure. |
Control | The user can view, edit and configure the structure - including changing structure permission rules and configuring synchronizers. |
...
Users who have Control permission on a structure can define permission rules by Editing Structure Details.
Permission rules list is an ordered list that's used to calculate the access level for a given user. Each rule has a condition that is matched against the user, and access level which is set if the condition matches. The conditions are applied from top to bottom, and the last matching rule has precedence.
...
- Anyone can view, developers can edit, only the owner and admins can control:
1. View for Anyone
2. Edit for jira-developers (Group) - Any logged in user can edit, except for the users from structure-noaccess group, who can't even view the structure. Project administrators are allowed to control the structurestructure010:
1. Edit for jira-users (Group)
2. None for structure-noaccess (Group)
3. Control for Administrators of Mars Colony (Project Role) - Incorrect configuration: everyone is given View access level Although the configuration looks ok at first glance, remember that the last matching rule has precedence. So regardless of whether the user is part of jira-developers or jira-users group, their access level will be set to View by the last rule.
1. Control for jira-developers (Group)
2. Edit for jira-users (Group)
3. View for Anyone
...
If you set Require Edit Issue Permission on Parent Issue flag on the Structure Details page, additional per-issue permissions checks will be performed to decide whether the user is allowed to change the structure.
...