Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Permission to prevent user group from adding/ removing backlogs in Active Sprint.

After doing some digging, seems like the "Schedule Issues" permission is what controls adding/ removing backlogs into Active Sprint. However by removing this ability for some users, will it also remove it for prioritizing the backlog?

Example Scenario: The PO needs the ability to prioritize the backlog, but not the ability to add/ remove backlogs into an Active Sprint as it is the Scrum Master who protects the Active Sprint in order to prevent overloading capacity.

1 answer

0 votes
Ignacio Pulgar Community Leader Mar 22, 2019

Hi Erik,

Ranking backlog issues requires Edit Issues & Schedule Issues permission.

So, yes, users you remove schedule issues permission would become unable to prioritize issues in the backlog.


So is there a way to accomplish the example scenario with permissions?

Ignacio Pulgar Community Leader Mar 26, 2019

I'm afraid there's no way to achieve that with permissions, or any other method that I know.

The most similar thing you may achieve would be manually controlling moments in which the people who should have limited permissions have, or don't have the Schedule Issue permission.

The process would be:

  1. Set the Schedule Issues permission to be granted just to a dedicated role (ie: Schedulers).
  2. Add the user group to that role in moments in which you want that group to be able to rank issues in the backlog or add/remove issues to/from a sprint.
  3. Remove the user group from that role when there's an active sprint and it is essential that they do not add/remove issues to/from the sprint.

Hope it helps.


I have the similar question, if I want to change the permission of Jira users than how it will be easy to do that. Actually I don't want to provide permissions to add/remove any of the backlog as its managed by Product Owner in our Project.

Would you please help me out in this? 





Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

193 views 6 7
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you