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.
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.
+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.
These issues in the JIRA backlog look related to this question:
|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
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.
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:
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!
Hello Community! We thoroughly enjoyed this just-for-fun conversation in the Jira Admin Group about what it's like to be a Jira Admin. For #JiraJuly, our talented designers created these graphics t...
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