What's the best way to limit users in putting stories in sprints? (Scrum board)

[Sherwin Soriano]

Hi!

We are having problems to a point where stories or tasks are flooding specific future sprints in one of our squad.

We want it in a way to put a control that only project administrators can put stories into sprints. This means that all other users will create stories and only has the option to put in backlog and coordinate with the project admin first.

Appreciate any ideas

[Bill Sheboy]

Hi @Sherwin Soriano 

Although you could use Jira permissions to manage this, what do you want to happen if the project admin is unavailable when a sprint is being planned?

The symptom you describe may have additional root causes leading team members to alter sprint scope without the participation of the entire Scrum team.  Please consider discussing this with the team in a retro to learn the causes, and how the team could experiment to improve.

Kind regards,
Bill

[Sherwin Soriano]

We did consider this, we have a number of project admins that are across all our JIRA projects anyways... appreciate the input as well :)

[Mohanraj Thangamuthu]

Hello, Good day. Please go to project settings >> Permissions and restrict the "Schedule issue" permission to a few required users. This should help. Thanks

[Sherwin Soriano]

I checked this setting, the "Schedule Issue" says "Ability to view or edit an issue's due date".

It does not restrict users to add sprints or edit sprint inputs.

[Mohanraj Thangamuthu]

Thanks for the update. Any user who don't have "Scehdule issue" permission will not be able to edit "Sprint" field on Jira issue. Please test with one user and check if this meets your requirement. Thanks