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

Jira Automation - close an issue a set number of days after event


I want to have a rule where an issue is automatically closed after it has a specific status for a set number of days.  

We get client queries that we raise as the Question issue type.  After resolving we need to wait for client confirmation that an issue is sorted, so we're just now setting them to the status "Awaiting Customer".  We are planning on closing them after three days if we get no response, but would like to automate it.  Any ideas?

So something like: 
When issue transitioned to "Awaiting Customer"

If no Changes to status after three days then close issue

Else do nothing

1 answer

Hi Sandy, 

Its already a known topic here:

If you go down in this page, I like the approach of Harry Heathcote using Automation only (no SLA) or also Italo Qualisoni [e-Core] using Automation and JQL filter... for example: 

status = Closed and updated < -3d



Hi Dam, I think you replied as I was editing the question so I don't think that will work.  We may be updating the issue within that three days and wouldn't want that to reset the clock. So it'd need to be "status not changed in 3 days" then close issue but I can't see that working in JQL.  

aah :) in JQL you can do: 

status = Closed AND NOT status CHANGED AFTER -3d

This is a valid JQL search, but I'm not 100% sure about the result cause I don't have the set of data to test this JQL but it should do the trick :) 

Can you please try and let me know? 


Like Taranjeet Singh likes this

@Sandy Greenberg did you had a chance to try the JQL filter I suggested? :) 

I just have now @Dam as your comments came after I logged off for the day. 

The JQL "status = xxxxxxx AND NOT status CHANGED AFTER -3d" certainly seems to work.  I'll have to give it a try in my test project with the automation to see if the scheduler does what I need it to do.  

Thinking about it @Dam I still don't see the solution on that page working.  If I use the automation to set a due date when I set the status to "Awaiting Customer" and then use that date to auto close it after a time period that JQL wouldn't pick up other changes in the issue.  I need a query and automation that will only transition the issue if there were no changes at all to it in that three day period.  

Humm I see... "no change at all during that 3 days period": this is quite hard to do in JQL... 

The CHANGED operator can be used with the Assignee, Fix Version, Priority, Reporter, Resolution, and Status fields only.

I will think a bit more about that, but I'm afraid this is impossible to do @Sandy Greenberg


Like Sandy Greenberg likes this

You will need to use the Updated date field in the JQL... this field is updated every time an update is done on an issue.

So the JQL filter should be: 

status = "Awaiting Customer" AND NOT status CHANGED AFTER -3d AND updated <= -3d

 @Sandy Greenberg I want to find a solution :) it's an interesting usecase. 

Let me know if this filter is working better or not... 


Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Atlassian Automation

Jira Automation: Sum Up Story Points Roundup (Initiatives -> Epics -> Story/Tasks -> Subtasks)

Hi Everyone, In this roundup we combine all the jira automation rules to sum up story points across different issue types. We start from the lowest level, summing up story points from sub-tasks t...

1,785 views 2 7
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