I want to control the sprint access(start/stop/edit) for the users in one of my next-gen projects

[Tony Tom]

I've created a separate role in my project without the sprint access, as specified in the documentation. The purpose, as mentioned in the title is to create users who don't have the ability to create/edit/change sprints.

But even after creating the user role and assigning the same user role to the users, they're still able to edit the sprint. 

Any idea on how to deal with this in a next-gen project? 

[Phill Fox]

Hi @Tony Tom 
I assume the documentation you have reviewed includes 

https://support.atlassian.com/jira-software-cloud/docs/next-gen-permissions/

On this page you will see the default settings for the critical permission (manage sprints) is as follows

viewer - not granted

member - granted

administrator - granted

Now I am assuming that you have correctly set up the new role with a permission of not granted. 

But I wonder if you have also removed your users from the member role?

If you could check those two points first then we can dig deeper if they are both correctly setup for your users. 

Hope this helps. 

Phill

[Tony Tom]

Phill

Thanks for replying. Yes, the one you linked is the same documentation I referred for this. I'm also aware of the permissions for each role. 

I've created a new role, by cloning the member role and removed the 'manage sprints' permission from that role. I've also assigned the same role to the users as well. 

Still, the users are able to edit the sprints. 

FYI I've only tried with the sprint which was created before these permissions were changed. Would that be something creating the issue? 

[Phill Fox]

Great @Tony Tom we are both working off the same understanding then. 

So now you have checked that the manage sprint is not in your new role permissions.

Did you also check that the users were not in both roles? Members and "new role" as they would still have the manage sprint permission from the original members role. 

It is worth remebering that users inherit the permissions granted from the combination of roles they are a member of. So if a user is in the role members and in the role "new role" one of which has a granted permission and one a not granted permission then because they are in both they are granted the permission. 

The behaviour that you are describing would apply to a user who has the original member role and your new role assigned to them.

I would not expect previous sprint items to be the cause but you can always create/destroy new sprints to check if a user has the manage sprint permission. 

Phill

[Tony Tom]

Phill

I understood the problem. Do you have an idea on how I can check the older permissions? Because I cannot find them in the project settings for a next-gen project. 

[Phill Fox]

Hi 
If you go into project settings - access then find the pulldown list for roles. Tick the option for member and you will then see all the users who still have the member role.

You can then go through each one and make sure that they only have the appropriate role selected. 

Phill

[Tony Tom]

Hey Phill

I've checked if there are multiple access roles for members of my project.

There is only one access role for everyone in my project. Still, the issue with starting, editing the dates, completing the sprint is there. 

I'm attaching a screenshot for your reference below. 

[Phill Fox]

Hi @Tony Tom 

I have just run through on my cloud development instance and reproduce your exact scenario which leads me to think this is a bug that should be raised with Atlassian on jira.atlassian.com. 
Here are the steps I took to reproduce the scenario. 

1. Switch on backlog/sprint feature

2. Create a test user and have them in member role

3. Confirm test user can create/edit sprints in backlog view

4. Create new role (No Sprint Permission)

5. Assign test user to only the new role (making sure to remove Member)

6. Check and find test user can still create/edit sprints in backlog view

So as you can see I can confirm that the restriction does not appear to be taken account of. 

Sorry I have not been able to help you resolve this but hopefully this at least lets you know that you are not alone. 

Phill

[Tony Tom]

Yeah, exactly. What use is the permission if it doesn't work. I'll raise this bug there. Thanks for the help @Phill Fox !! Appreciate it :)