How to allow people to create sprints without giving Admin rights?

[murali krishna]

How do I allow people to create sprints without giving them admin rights?

I want to restrict admin rights to very few people in my organization.

Now I have got 6-7 manager asking for admin rights as they cannnot create sprints.

[Nic Brough -Adaptavist- · Accepted solution]

You don't give them admin rights.

They need to be *project* administrators, in the project(s) they need to create sprints for. They don't need to be system admins.

Project admins get sprints, users (just adding/removing people to/from roles) component and version maintenance.

[C_ Faysal]

exactly.

if you wanna read more bout that topic check this KB

https://confluence.atlassian.com/display/JIRA/Managing+Project+Permissions

[Nic Brough -Adaptavist-]

(In fact, I forgot - I'm a system admin. I can NOT create sprints in 797 of our 800 projects - only the Jira and Confluence ones...)

[C_ Faysal]

Nic so i am. i guess your default permission scheme doesn't include jira-system-administrators in the Admin role right?

i did a similar setup to avoid seeing and reveiving unwanted jira content/notifications :)

[Nic Brough -Adaptavist-]

Dead right - I look after their system, not their data! I always try to work with a system-admin account that has minimal groups and roles, so that when someone says "I can't do X", I can work with an account that probably replicates the behaviour. (Plus, I honestly don't have the time or energy to worry about the 480,000 issues that aren't directly affecting me...)

[murali krishna]

It worked, I removed project admin from JIRA-Admin group.

[C_ Faysal]

At least nics answer should be the one to accept instead of your own....

[murali krishna]

Thanks Nic, I will try this and get back to you.

[Nic Brough -Adaptavist-]

Try it with one permission scheme first, there's no need to plough through all of them if you then find out it's not really going to be right for you.

[murali krishna]

In our JIRA, project administrator is part of "JIRA-Administartor" group.

Does it mean "project administrator have all permissions that a JIRA-administer will have?

[Nic Brough -Adaptavist-]

Yes. Remove them from the jira-administrator group. They don't need it.

The best way to do all of this is to change your permission schemes. I usually start from:

Create a new "role", called something like "project admin"

Change *every* permission scheme you have - on the line that says "project administration", add "role: project admin", and remove all the others.

It's often a good idea to include "project lead" in the "project administration" line, but that's up to you.

(At this point, consider leaving jira-administrators on that line - it might be appropriate for the way your organisation works, but if you remove it, there's nothing to stop your admins temporarily adding themselves if they need to)

For each project, add the relevant users to the role of "project admin".