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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to use Automation condition JQL 'status was Done'


I'm trying to accomplish the following: do an Automation action of a ticket is pulled to Done not the first time. My idea was to use the JQL condition 'status was Done', so the Automation would do the update when the JQL is true. 

For some reason, the automation runs even for the first time although the ticket was not in the Done status before.

I've tried it putting in an if condition block and add the action to it, but I experience the same behaviour.

It seem that the condition checker evaluates the status after is has been executed.

Please advise how to set up the automation rule.




Screenshot 2021-01-25 at 16.28.37.png


3 answers

1 accepted

0 votes
Answer accepted
Alexis Robert Community Leader Jan 25, 2021

Hi @Laci Kremer , 


I would look into the JQL condition, something like "status was done BEFORE -1d" or something like that. With the BEFORE, AFTER and DURING operators you can specify when the action was done.


let me know if this helps, 



Thanks, 'status was Done before -1m' does the job!

Like # people like this

Hi @Laci Kremer  -- Welcome to the Atlassian Community!

Would you please clarify what problem you are trying to solve with this rule?

It would seem there is something you want to do when an issue moves to Done, and that issues can move to Done multiple times.  That may indicate you are actually missing steps in your team's processes (columns/status values) if you are moving things backward and forward as part of your normal working practices.

Best regards,


Hi Bill, 

We don't want to optimize for chaos for sure :)  Yes, tickets should not move backwards, but life happens. The process has more steps, and there are situations when a ticket needs to go back a step and move forward again. We'd like to track these situations.



Like Bill Sheboy likes this

Thanks for explaining, Laci. 

This seems like a "watch for defect rework" type of situation.  If so, couldn't you just count/increment when an item moves from Done to earlier in workflow (transition from Done to anything, except for cloning)?  Just an idea...  Thanks!

0 votes
John Funk Community Leader Jan 25, 2021

Hi Laci - Welcome to the Atlassian Community!

I think the WAS IN condition will include those just moving to it. 

One way would be to create a custom number field and default the value to 0. 

Then on a post function to Done, set the value to the current value +1 using Automation.

Then in the above condition, only look for those cards that have a value of = 1. But before you do the condition, add another step prior to Re-fresh the issue to make sure the value gets updated first. 

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira

Announcing the waitlist for Jira Work Management

Hey there Cloud Community members! We’re excited to give you the first glimpse of the new home for business teams on Jira — Jira Work Management. Jira Work Management is the next generation of J...

863 views 14 20
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you