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

JQL to Find Issues Updated/Changed by Assignee/Reporter

Use case:

We don't have JIRA service desk but would like to send out 3 custom reminder emails for to the original requester (or Current Reporter/Asssignee) if the issue has not been updated for X days (1 day | 5 days and auto close)

Plugins Involved:

1) JIRA Automation Lite = used to schedule and auto-transition issues
2) Email This Issue = used to send out custom emails


I can't seem to find an appropriate JQL syntax to do this?  Any way to do this without Script Runner?


1 answer

1 accepted

1 vote
Answer accepted

There has to be something that shows that you have already sent the reminder... so what we do is to set a flag. We have a field called "Reminder" which is available to the project but not shown on the screen.  Then we can use the jql:

project = ABC AND Reminder is EMPTY AND updated < startOfDay(-1)

Then using automation, we send an email and set the flag. Or in your second case to also "Auto close" the issue.  

Hi Rodney!

Thank you for the input!  After messing around with it for a bit, I came up with an Automation Rule like below to find issues that need a Reminder Email (Runs twice daily) to fire a Generic Event by a service account (JiraAuto):

project in ("ABC", "EFG") AND status = Resolved AND resolved <= -1d AND updatedDate >= startOfDay(-1) AND updatedDate < endOfDay(-1)

I then use another rule to find the issues that need to be Closed with the following (Runs twice M-F only) to Add a silent comment and Transition to Close by a service account (JiraAuto):

project in ("ABC", "EFG") AND status = Resolved AND status changed before -5d AND updated <= -5d

Then, I use Email This Issue (JETI) to look for Generic Event and Issue Closed Event with the appropriate JQLs to fire off the emails.  Did a few testings and it looks like it's been working great so far.

What you have provided will prevent a duplicate email being sent out in my first rule, which will most definitely help and I'll add it to my setup!

P.S  Do you set a Post-Function to clear out the Reminder field if an issue is Reopened to make sure it works properly in the second cycle?

Yes... When there is a reopen we clear the Reminder field and the Resolution field... starting it over again

Thanks Rodney.  Appreciate the input.  Hopefully someone else will also find my setup helpful for future uses... Cheers

Suggest an answer

Log in or Sign up to answer
This widget could not be displayed.
This widget could not be displayed.
Community showcase
Posted Wednesday in Jira

Upcoming Enterprise releases targeting Q3 2019: Jira Software 8.5 & Jira Service Desk 4.5

Since launching the Jira Software 8.0 and Jira Service Desk 4.0 platform releases in February, many of you have been asking when the next Enterprise release will be so you can take advantage of the m...

324 views 3 7
Join discussion

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you