Any Way to Prevent Closing a Ticket Unless It Has a Certain Status

[Andy Harper]

Greetings,

I use Jira for our change control process.  All change control tickets are supposed to be reviewed and documented by me accordingly.  However, some people are closing tickets before they are reviewed.  Either intentionally to sneak things past my review or unintentional because they forget to change the status from "Planning" to something else.  I'm looking for a way to prevent one of two scenarios (I've included screenshots):

In the first one, I'd like to prevent a ticket from being "Resolved" or "Closed" if it is still marked "Planning" as seen below.  The reason being is if a ticket is done, it should no longer be marked "Planning" as work was obviously done on the ticket.

In the second scenario I would like to prevent a ticket from being "Closed" if it is still in "Review Pending" as seen below.  If it's "Closed" and hasn't been reviewed, then how do I know they followed the change control process properly (i.e., was it truly a Pre-Approved change vs. something that should have gone before the change advisory board)?

I have a search string that will manually catch these things but I'd rather they do it right from the beginning rather than me run my search and tell them to go back and fix their tickets.  Any help or advice would be appreciated.  Thanks.

[Josh Steckler]

What does your workflow look like? Are you using global transitions?

The Suite Utilities for Jira add-on would give you the ability to have workflow conditions based on the value of a field or workflow status. I understand buying things is usually a pain, but this adds a lot of functionality that I couldn't live without as a Jira Server admin.

Without an add on, building your workflow to have these conditions won't really be possible, but you can do things with permissions instead (requiring a special role to close issues).