Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How can I ensure an Automation rule only runs once for an issue?

andreas Rising Star Oct 10, 2017

I want to ensure we only run a particular rule one time against an issue. How can you do this with Automation for Jira?

1 answer

1 accepted

3 votes
Answer accepted
andreas Rising Star Oct 10, 2017

So there's a few different ways this can be done. A visible way would be to edit the issue and add a label, then check for the presence of this label with a JQL condition.

Another way that's invisible to users is to use entity properties. Your rule would look like this:

  • Trigger: Any trigger
  • Compare condition:
    • First value: {{}}
    • Equals:
    • Empty (leave field blank
  • Action: Do something like editing the issue
  • Action: Set entity property 'ruleexecuted' = true


It looks like this in practice:



The actions in this rule will now only execute once for a given issue.  After that, the compare condition will fail since the issue property has a value.

@andreas what happens when needed to run another rule once, but the {{}} = true because it was edited by another rule.


The {{}} is for every particular rule or for all rules? i.e. an issue can only have one value or it can have several values for every rule?

This is because i have this compare condition en Epics but is telling me on the audit log that the issuesdid not match the condition: i.e. is nos Empty.



Like Jean Francois Gelinas likes this

That doesnt work since you cant execute another rule for that issue.

@andreas The first condition always fails. I assume because {{}} is not even an existing issue entity. Did this work for you? Any clues why it will always fail for me

This works for me with 5 separate rules. I named the properties 'rule1executed', 'rule2executed', rule3executed', etc. I used this to generate child issues when the status is changed. 

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events