Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Users unable to manage sprints

Patricia Johansson
Contributor
February 27, 2023

We're experiencing issues that multiple users cannot start/complete sprints, the button is greyed out saying that the permissions are missing.

The boards in question are based on "complex filter" such as:

project in (proj1, proj2) AND labels in (label1, label2)

 

We just have one permission scheme which allows users from the group jira-user to manage sprints. Jira-user is out default group that all users are added to. So in theory each user should be able to manage a sprint in any project, however for these cross project boards we seem to have an issue.

It seems I can't replicate this issue as I'm a site admin and org admin.

Any ideas of what could be the cause?

2 answers

0 votes
Trudy Claspill
Community Champion
February 27, 2023

Hello @Patricia Johansson 

As an experiment, can you temporarily modify the filter to remove the criteria for the "labels" field and see if that enables the start/complete sprint option?

You said you have a group and a role in the permission scheme. That should not cause a problem.

Have you absolutely confirmed that the user belongs to either the group or role that has the Manage Sprints permission in both projects?

Are either of the projects Jira Service Management projects?

Patricia Johansson
Contributor
February 28, 2023

Hi @Trudy Claspill

I did try changing the filter including having it only "project = projectx" and it still has the same behaviour.

I've confirmed with a separate user which was only added to the "jira-users" group and confirmed both projects allowed this permission to that group (in the case when I tested two projects in the filter).

We use the same permission scheme on all projects and this issue was resolved on another project by restructuring the filter query.

None of the projects affected are Service Management projects, both are Company Managed jira software projects.

I did notice that we had originally created a new project called "project A" and then it was decided that actually the existing project "project B" should actually be renamed to "project A", and the previously created was moved to trash. I ensured this project was permanently removed as well, and still same issue. I guess it could take some time to update maybe

0 votes
Somnath Patil
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 27, 2023

Hi Patricia,

 

To Start and Complete Sprint you need the following permissions:

Browse Project, Manage Sprint, Edit Issue and Schedule Issue.

Patricia Johansson
Contributor
February 27, 2023

Hi @Somnath Patil

The permission scheme we have for all projects has all those permission applied to the group "jira-user" which is our default user group.

Is there a chance that having a group specified as well as project role in the permission scheme could interfere with each other? 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events