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

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.

4 answers

1 accepted

1 vote

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.

(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...)

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 :)

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...)

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?

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".

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

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.

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

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

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published 7 hours ago in Agile

What is ChatOps? A guide to its evolution, adoption, and significance

I am the product of AIM. I can hear that door swinging open and closed in my mind with absolute fidelity. I’d recognize that ding anywhere. At 15, as I typed away into AOL IM, I never imagined that ...

22 views 1 5
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you