Limiting Sprint Permissions in Active Sprints

[Kelly Ballwanz]

I've read the old questions/answers, but haven't seen anything recently.  So checking to see if there have been any changes that would allow us to limit who has the ability to add/remove tickets from ONLY the current sprint.  

We want our team to be able to add to future sprints, for planning purposes.  But once a sprint is started we'd like to limit the ability to add tickets to only Product Owners. 

Is there any way to do this?

[Trudy Claspill]

Hello @Kelly Ballwanz 

Which old posts have you referenced?

There is no project permission that is specific to adding issues to active sprints.

You might use an Automation Rule to detect that the Sprint field for an issue has been changed, and then check if the issue is in an Active sprint. If those conditions were met that would mean that an issue was moved into an Active sprint. You can add another condition to check the rule initiator. The rule can't prevent that addition from happening but you could at least generate an email when it does happen. It might be possible to remove the issue from the sprint, but I haven't tried to do that myself.

[Shiva Kumar Hiremath]

Hello Kelly,

can you try with following automation

[Trudy Claspill]

Hello @Shiva Kumar Hiremath 

That rule will not accomplish the requirement.

That rule is triggered when a sprint is started. It will not be triggered by changes to issues such as the update of the Sprint field when an issue is added to a Sprint.