You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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
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?
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
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. https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-fields/#Updated
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...
Hi, @Sandy Greenberg
I’ll try to help you. If you want a rule where an issue is automatically closed after it has a specific status for a set number of days, you can install plugins that offer such an opportunity. For example, SLA Time and Report for Jira add-on and do the following steps:
Set status change to Resolved
Don’t forget to check your workflow.
You need to have the ability to move to Resolved if this status was chosen.
Create a task and change status to Waiting for customer
Wait until your time goal happens.
After 72 hours the status will be changed automatically.
I hope this is what you need.
Also, this add-on is created by my SaaSJet team, so if you have any questions, I’m here to answer them.