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

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?

Accepted answers

Davin Hoekstra

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.

All comments

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.

Davin Hoekstra

Hey Folks,

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.

Aniket Patil_m7khcb

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!

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-software

permission