Prevent users adding items to current sprint

I would like to stop some users adding new issues to a current sprint. Seems strange that I can stop people moving issues up and down the backlog priority list but I cannot stop people from adding any issue they like to the current sprint. Any ideas?

2 answers

1 accepted

This widget could not be displayed.

Hi Simon,

You need to configure the 'Edit Issue' permission in the project to which the issue.

Hope its help.

Regards,

John Chin

Thank you John, very helpful.

I don't think that's really a solution to what's being asked here. The goal is to prevent a user from adding an issue to (or removing an issue from) the current sprint. Not to prevent them from editing issues entirely.

This is generally relevant to non-developers who are acting in a 'stakeholder'/'project-manager' kind of role. They should be able to prioritize the tasks that are in the backlog (i.e. anything that is *not* in the active sprint), but they should not be able to touch anything that is in the current sprint. At least not in terms of removing it from the sprint, or arbitrarily dropping new tasks into the sprint.

That's not a solution John. Adding scope to a sprint is different from editing an issue. All developers etc need to be able to edit issues or they'd have to call me each time to edit it which would be silly. I need to stop developers from just adding stories mid-sprints.

+1 David. I need that as well. I have a client that refuses to play by the rules and keeps trying to sneak issues into the current sprint.

+1 We have users who add issues to sprint without the authority to do so. Preventing that via a new permission would be perfect.

This is not the solution, @John Chin Kim Loong. Adam Roth desciped the issue very well in the comment above.

This widget could not be displayed.

Hey Folks, 

Simple fix. Ensure your Permission Scheme has limited roles (like just admin or Project Lead) assigned in the Schedule Issue permission. Only folks in the Schedule Issue permission can add due dates to issues and move them in and out of sprints.

Many of our users need to update due dates but only one or two should ever be able to move issues in/out of sprints. Is there a fix for that?

If your users have the ability to set due dates, then you're allowing them to determine when issues will be done. That's the same as adding issues to the sprint as that person is scheduling the issue. If you want to have a desired date that anyone can populate just create a custom field so they can indicate a desired completion date but not add issues to sprints. It's more of a request than a mandate then.

Setting due dates and putting items into sprints are not really the same thing, at least not for us and the way we are using Jira. We have several kinds of issues that operate within a sprint, and the due dates are not always tied to the sprint time-frame. I appreciate the suggestion. A custom due date field would successfully allow the Schedule Issue permission to work separately. As long as Scheduling doesn't control any other behavior we wish to allow for the larger user pool, I think this would work.

I would like for our users to be able to move tasks in and out of Future Sprints, just that they can't move a task in and out of an Active Sprint, unless they have admin rights. Does this solution apply there?

I have the same request as Selvam above.  I want to be able to prevent adding to active sprints.

I would also like to prevent users from moving tasks into an active sprint. Has a solution been found yet?

I am also interested in getting this permission feature.  Is there a more formal way to make this request?

+1 I need this feature too! any update from Atlassian?

 

I agree - this is a pretty fundamental capability in the deliniation of roles between the technical team and the product team - in fact I thought I had a recollection of this being possible back in JIRA V4 with Greenhopper.

 

 

 

+1 It would be really useful to us as well to be able to restrict permissions on adding issues to the active sprint and future sprint separately. Idea being that everyone in the team should have the permissions to add issues to a sprint but at the same time ensuring that the workload in the active sprint can't easily be added to. 

Atlassian announced new changes to the permission scheme options at the conference this month. It will grant you the ability to let other roles add fix versions and components but I'm not sure Schedule Permissions is being split up. The IM/Scrum master is responsible for dependency management so you likely don't want people re-ranking your backlog. If you do, then just ensure they know their roles and responsibilities to re-rank blocking stories when they touch the order of the backlog and grant them Schedule rights.

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted yesterday in Canada

AUG Lunch Roundtable - August 13 - Highlights

Thanks to everyone who came out today for the lunch AUG - we had some great food and discussion (and ice cream sandwiches to fend off the heat!) The welcome and fun fact was great as well, what an aw...

28 views 1 3
View post

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you