A user must not be allowed to change the status of a subtask unless the preceding subtask has been c

[Julina Del Rosario]

I'm working on a project, and one of the rules is: the user should not be allowed to change the status of the next subtask if the current one is not yet completed. If anyone can help, I'd really appreciate it. Thank you

Example: The user should not be allowed to change the status of Technical Design if the Business Requirement is not yet approved or completed.

[Trudy Claspill]

Hello @Julina Del Rosario 

How do you know which subtask is the immediate predecessor of the subtask attempting to be updated? Have you created dependency links between subtasks?

You must first have some method of determining the predecessor subtask from the information available in the subtask you are trying to change. The method must be something that can be assessed by Jira, such as looking a link relationships, or looking at a field in subtask #2 that has the key for its predecessor subtask.

Additionally, there is not a native function in the Jira workflow capabilities to block the transition of an issue based on a predecessor issue's status. There are third party apps that can add such capabilities to the workflows, if you are open to considering that.

Without a third party app you would have to implement a work around, such as using an Automation Rule to set a field in the subtask when its predecessor subtask transitions to done. Then add a Condition in the workflow to block transitions if that field has not been set appropriately.