How to Prevent Accidental Closure of Sprint Before End Date in Jira?

Dharmraj Chauhan

I am looking for a way to prevent the accidental closure of a sprint before its scheduled end date in our Jira setup.


In our Jira instance, admin access to the team board is granted to specific roles such as the Scrum Master, Product Owner, and other higher management personnel.

Recently, we encountered an issue where the Product Owner accidentally closed an active sprint before its scheduled end date. For example, the sprint started on January 1st and was supposed to end on January 15th, but it was mistakenly closed on January 10th.

 

Is there a built-in feature or a configuration in Jira that allows us to set such a restriction? If not, are there any plugins or custom scripts that could help us achieve this functionality?

 

Thank you,
Raaj

Clark Everson

Hi @Dharmraj Chauhan 

There is no built in feature to do this. Anyone that has access to close sprints can close them at anytime.This is because if al work in a sprint were finished early, you wouldn't want to bring new work into a sprint from a reporting standpoint, at that point a new sprint should be started

With that said if you want to do this you would need to remove permissions from all users that have the permission to start and end sprints, and then I would create a service account for it. Then you would need a tool like scriptrunner to run a script to trigger this action as I don't think automation for jira can do this

Alternatively you could build a custom app using atlassian forge for this, but would still need to remove those permissions from users

https://developer.atlassian.com/platform/forge/

Best,

Clark