How to add "Stop Rule Execution" action in JIRA automation rule?

[Ashish Nayak]

I want to stop the JIRA rule execution if the condition is not met. But I did not find the trigger action as a stop rule execution. Can you help me?

[Trudy Claspill]

Hello @Ashish Nayak 

Welcome to the Atlassian community.

There is no such action for Automation Rules.

If a condition is not met then the actions that follow it will simply not be executed. There is no need to explicitly stop the rule execution.

However, if you show us your rule and explain the process you are trying to automate, then we can help you verify that it is structured correctly or suggest how you need to modify it.

[Ashish Nayak]

Hi @Trudy Claspill ,

Thank you for the response. I create rule for the below condition,

Move Parent Story to 'Ready for QA' when all the Development Sub-tasks are Done and QA Sub-task Exists in any of the status.

Please find the attached screenshot for reference.

[Trudy Claspill]

I believe this is the rule you need:

1. First confirm that the issue triggering the rule was a Dev Sub-task.
2. Branch to the sub-task's parent
3. This will confirm that there are not any Dev Sub-tasks set to any status other than Done 
4. This will confirm that there are some QA Sub-tasks under this parent issue.
5. If both 3 and 4 are true, then transition the parent issue to the desired status.

If either 1, 3, or 4 are not true, then none of the steps that come after the not-true condition will execute and the Parent issue status will not be changed.

[Bill Sheboy]

Hi @Ashish Nayak 

Just following up to check if this answered your question.  If so, please consider marking this one as "answered".  That will help others with a similar need find solutions faster.  If not, please let the community know what help you need with the rule changes.

Thanks!

[Bill Sheboy]

Hi @Ashish Nayak 

Something is curious about the rule image you show: there is no such feature as nested branches in Jira Cloud, Server, or Data Center at this time, but your image shows nested branching.

There was a defect that allowed dragging a branch inside of another one while editing a rule, and that produced undefined / unpredictable behavior until it was fixed (for Jira Cloud).

Please explain how you created that rule, and if it is indeed an Atlassian Automation rule image.

Thanks, and kind regards,
Bill