nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JIRA Agile Create Sprint Permissions

KP11

How do we give a userid permission to create a sprint in Greenhopper without giving full admin access?

I had to put the userid in jira-administrators group so they can create the sprint in a managed board created by the user

He was in "Administer Project" for the only project in his backlog section of managed boards

Accepted answers

Henning Tietgens

The user has to have 'Administer Projects' for all potential projects where issues can be found by the boards filter. If you don't restrict the filter on which the board is based to one or more projects, the user has to have project admin rights for all projects in your JIRA system.

Henning

All comments

Timothy

(info) Note that you can only create a new sprint if you have the 'Administer Projects' permission in all projects included in this board's backlog.

Source: https://confluence.atlassian.com/display/GH/Creating+a+Sprint</span<>>

KP11

The user was in the "Administer Projects" section and there was only one project in the backlog section view. The Create Sprint was greyed out until we gave him full admin access to the group. His userid was in Jira-Developers and userid was in Administer Projects. Are you talking about the JIRA roles section? You mean Permissions! He is in both and still greyed out. We tried removing and putting him back in Jira-Administrators to verify?

Any other ideas Roles? Permissions?

His Board Filter : Filter Query

project = FND AND issuetype = Bug AND "Target Release" in ("5.0.0.0 ", "5.0.0.0 SS") ORDER BY key DESC

Administer Projects
Ability to administer a project in JIRA.

Single User (RichB)
Project Lead
Group (jira-administrators)
Single User (JohnS)

KP11

Checked all the above. Still greyed out untill we put him in Jira-Administrators

KP11

It seems that we cannot create sprints if the SHARES are : Shared with all users

Henning Tietgens

Henning

Peter Molettiere

I'm having the same issue. A user can not create or close sprints. User belongs to a group (we're calling it "scum-masters") which is granted Project Administrator access on the project. The filter includes "project = projectname" for the project.

Peter Molettiere

I had to make the "project = <project name>" clause the very first clause in the query. "custom field = foo AND project = <project name>" doesn't work, even though it conforms to the guidance above.

Jon Graf

You also have to "Use Ranking" in the Filter config.

Rob Fagen1

One other issue that I've noted is that if an issue has been moved between projects, then in order to start a sprint on a board including that issue, you have to have admin on both the move-from project and the move-to project.

Marc Minten (EVS)

Rob, thanks for this info. I think we are running in the same situation. Board filter = "Project = Xxxx AND ...", still prople have to be admin of some other project(s) in order to create/start sprints. Indeed we moved some issues.

@Atlassian: really, this is crazy behaviour. We are loozing hours to fiddle out, assigning/revoking project admin rights. Giving all people that can create/start sprints admlin rights on all projects is really NOT an option.

Simone Longoni

I believe this is related to this outstanding feature request, planned to be addressed within 12 months: https://jira.atlassian.com/browse/GHS-5035

Simone Longoni

I believe this is related to this outstanding feature request, planned to be addressed within 12 months: https://jira.atlassian.com/browse/GHS-5035.

Please vote it to get it done sooner... :-p

Nathanael Motz

I believe https://jira.atlassian.com/browse/GHS-6850 relates to this problem.

Marc Miller

Simple answer to the original question: Assuming you have created a permissions scheme that is a copy of the default (so you don't muck up the default settings), edit that scheme (the copy) and under Administer Projects, ADD another project role that holds specific people that you want to do Project Admin tasks. For example, I have created a project role called jira-managers to which I add project admins, and then add that role to the permissions scheme under the Administer Projects permission. The new permissions scheme must of course be associated with your project.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-software

board

permission