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; } } }

Users are not able to change sprint value on issue page

Kaushik Patel

I am facing an issue where admin users are able to change the sprint selection to any future sprint but any other logged in users cannot.

In the project permissions we have set Schedule Issues >> any logged in user

Edit issues >> any logged in user

Despite of this selection, the users are not able to change the sprint value.

Note: We created new sprints after we migrated to JIRA Cloud in early Dec and after this, users are having this problem. Users are able to change sprints to any older sprint values.

Can someone assist here?

Thanks,

Kaushik

Accepted answers

All comments

Nic Brough -Adaptavist-

Have you given your users the permission to manage sprints?

Kaushik Patel

Yes, it is set to

Application access (Any logged in user)

Nic Brough -Adaptavist-

Ok, and do your users have product access to Jira Software? (Sorry, I should have asked this first, but I forgot. Another conversation has just reminded me)

Kaushik Patel

Yes, users do have JIRA software access. They are able to change the sprints (past sprints before migration happened)

Kaushik Patel

hi @Nic Brough -Adaptavist- I tried some combination of user access today. I found that admin users are able to change sprint value to future sprints. The non-admin users can't change sprint value of future sprints, in fact, they don't get the drop down of future sprints.

It seems there is some permission/access related issue here because when I make non-admin users admin and try the same test, they are able to change value to future sprints.

Thanks,

Kaushik.

Nic Brough -Adaptavist-

That means your admin role has permission to manage sprints, but ordinary users do not.

That's the only way to get what you are describing here. Check the permissions on your project, but also have a look at the workflow - you can change permissions by putting properties on the steps in the workflow.

Kaushik Patel

Yes, the access of Mange sprints is already set as (Any logged in user)

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

permission

sprint

cloud-migration