Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Help with merging automation rules

Eric Roetenberg
Contributor
August 12, 2026

 

Hi all,

We’re currently using JMWE to ensure that Story Points are filled in when an issue is set to the “Done” status; if this isn’t the case, the issue reverts to its previous status.


I’d now like to achieve this with an automation rule, but I’ve already set up various actions using branches, if-else statements, etc. However, it boils down to having to create a separate rule for each status transition, as shown in the attachment.


So, if the transition is from A to Done and the conditions aren’t met, it reverts to A.
Since the workflow has 10 statuses, I’ve created 10 automation rules.

Is it easy to merge these, or is there another way I could have solved this?

I also have a JSON file, but I can't attach it here. If you email me, I'll send it to you. Eric.Roetenberg@Enexis.nl

 

grtz. Eric

safe workflow.jpg

 

3 answers

1 vote
Geert __ 2improveIT
Contributor
August 12, 2026

Hi @Eric Roetenberg 

Use a workflow restriction to block the transition silently, or a workflow validator to provide user feedback. See examples below.

restrict.gifvalidate.gif

Marc -Devoteam-
Community Champion
August 12, 2026

HI @Eric Roetenberg 

I second the reply from @Geert __ 2improveIT 

Use workflow validations or conditions instaed of automation to revert a work item to the previous status.

Prevent it or provide guidance to add it before the transition can be done

0 votes
Duc Thang TRAN
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
August 12, 2026

Hello @Eric Roetenberg 

You can leave the From status blank and set only the to Done as suggested @Lalithesh  , so the rule captures transitions from any status.

With this automation approach, the issue is moved to Done first and only then reverted. This unnecessarily consumes an automation execution and adds two transitions to the issue history.

In my view, if you are a Jira instance administrator, the cleaner solution is :
Identify all the workflows concerned and add a validator to every relevant transition to Done 

with an error message such as:

“Story Points must be filled in before the issue can be moved to Done.”

You could also add a transition screen containing the Story Points field. 

This blocks the transition  and avoids maintaining a global automation rule with complex conditions.

BR,

0 votes
Lalithesh
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
August 12, 2026

Hi @Eric Roetenberg 

Welcome to the Atlassian Community!

If your goal is to transition the work item back to the previous status from Done, then you can achieve it by using this smart value {{changelog.status.fromString}}

  1. Trigger: Work item transitioned
    From Status: Leave this blank, To status: Done
  2. Condition: Add conditions based on your requirement
  3. Action: Transition work item
    Add {{changelog.status.fromString}}
  4. Action: Add comment (if required)

This will automatically revert the status to the previous stage.

Hope this helps :)

Cheers!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
ENTERPRISE
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events