Prevent users adding items to current sprint

[SimonM]

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?

[Davin Hoekstra · Accepted solution]

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.

[Rex Parsons]

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?

[Davin Hoekstra]

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.

[Rex Parsons]

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.

[Selvam Raju Somalraju]

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?

[Charlotte Skogsholm]

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

[Kimberly Roberts]

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

[Systems Team]

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

[Martin Charlesworth]

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

[Oleg Appassov]

Muy helpful

[adavison]

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.

[Christof Spies]

This is not the solution. As Adam Roth wrote: "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 scheduling issues entirely.

[Bleddyn Raw-Rees]

+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. 

[Davin Hoekstra]

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.

[Linda Gardea]

These issues in the JIRA backlog look related to this question:
 

JSW-8964	Specific permission to add an issue to a Sprint (or remove an issue from a Sprint)
JSW-11969	Only those who have 'Administer Project' permission should be able to add issues to an active sprint
JSW-14633	Provide a separate permission for users to assign issue to Active and Future Sprint

I intend to vote/watch the original issue JSW-8964 

[John Chin]

Hi Simon,

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

Hope its help.

Regards,

John Chin

[SimonM]

Thank you John, very helpful.

[Adam Roth]

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.

[Davin Hoekstra]

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.

[Frank Vidal]

+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.

[Rex Parsons]

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

[Christof Spies]

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

[Aniket Patil]

For anyone looking for answers on next-gen projects, the answer is NO you cannot prevent the users from adding/removing the issues from current/planned sprints; however, the "Manage Sprints" permissions only talk about the following topics: 

• Create sprint
• Start sprint
• Complete sprint   

Therefore, if you have not given anyone permission to manage sprint, they will not be able to do the actions in bullet points above; however, they can still add/remove the issues from the sprints. Which is really really disappointing!