You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I have two users:
1 - a Jira Admin
2 - a non Jira Admin
Both use the same board to point to a single Jira Project
In the Permission Scheme, 'Manage Sprints' is undefined (it's empty)
Yet somehow the Jira Admin can 'Create Sprint' in a Jira Scrum Board, but the non-Jira Admin user cannot (as to be expected, the 'Create Sprint' button is greyed out)
My question is: how is it that a Jira Admin user can 'Create Sprint' even though the 'Manage Sprint' permission is undefined - does the Jira Admin have a 'hard-coded' (i.e. Permission Scheme ignored) 'Manage Sprint' permission?
Hi @John Funk - I haven't revisited this yet. I can see two other answers but neither seem to have answered my specific query: In the Permission Scheme, 'Manage Sprints' is undefined (it's empty) yet a Jira Admin can manage a sprint even though the Permission Scheme and Users and roles pair don't explicitly grant the permission, so I was wondering if it's hard-coded somehow...
I'll add it to my backlog and see if I can get to the bottom of this...
Jira admins, members of the jira-administrators group, are by default added to the Administrators project role for new projects. This can be configured differently, if desired:
Through the Administrators role they inherit several permissions such as Administer Project. This of course is also configurable as seen on:
Most likely there should be 3 types of users and not 2 (atleast applicable to my company)
1. Jira Administrator (responsible for managing Jira infrastructure & maintenance) - More like a super user / admin
2. Project Administrator - Who has access rights to manage project specific activities as well as management
3. Project users (developers / Scrum masters / Test Professional / Product owners etc)
Typically, a Project admin or Scrum Master is enabled to create a Sprint or manage a sprint being the role that they play in Scrum (This is specific to Scrum Master). Project Admin is meant for administration of the overall projects.
In many companies (or atleast mine), these roles can be defined by Jira Administrator for a controlled & managed environment of Jira for smooth functioning. So in short, Jira Admin needs to define roles but being a super user they practically get all feature access including Manage Sprint also !