Project Permissions
by Brands · 10 things on Twos
- Roles are commonly best case for project permissions
- Complete a sprint with unresolved issues -> Edit issues, Schedule issues, Manage Sprints, Browse projects (Issues will not be transitioned and keep their status). Schedule issues might also be required if the due date is being changed. Jira admins will already have the ability to manage sprints.
- Complete sprint with complete issues -> Browse projects, Manage sprints (Jira admins already have manage sprint perms)
- Rank issues in backlog -> Requires Schedule issues and Edit issues permissions (With Jira Software application access)
- Schedule issues -> the ability to view or edit an issue's due date.
- Resolve issues -> the ability to resolve/reopen issues and setting 'Fix Version'
- Manage versions and components comes under Administer projects and editing issues when applying the versions, these are not project permissions
- Delete All Worklogs/Edit All Worklogs -> Ability to edit or delete worklog, in combination with "Work On Issues"
- Site admins CANNOT manage the board
- There is NO specific permission to view reports, just requires browse project permissions