How to create alert for issues being in some statuses for too long?

[Joey Huang]

I want to receive email notifications (or to be tagged or alerted in some way) when tickets are in "Code Review" or "Deployed" statuses for > 3 days. 

I was able to set up a scheduled trigger to send me an email using JQL to filter for those tickets. However, the email sent to me had no content in the email body (ex. did not list the tickets that's been sitting in those statuses for > 3 days)

JQL used: project = SS23 AND NOT status CHANGED AFTER -3d AND "Dev Team[Dropdown]" = "Data Infrastructure (DI)" AND status IN ("Deployed to Dev", "Code Review")

[Najm Polaris · Accepted solution]

Hi @Joey Huang

The easier way to achieve this would be to create the JQL in advanced filter and save it. Schedule the JQL to send you emails as necessary. In this case you won't need the automation at all and it will send you the whole list of issues as you save in the filter view.

[Trudy Claspill]

That would indeed be an easier way to get the same data. :-D

[Joey Huang]

@Najm Polaris How do I "Schedule the JQL to send you emails as necessary."? Is it still under Automation? I used the following content but the email is just a blank email (not actually listing the issues in the email)

{{#lookupIssues}}
* {{key}}
{{/}}

[Trudy Claspill]

No, this is not under Automation.

In Advanced Issue Search enter the JQL you have for selecting the issues. Save that filter.

Next go the the Filters menu and select View All Filters.

Find the filter you just saved.

Click on the ... to the far right of the filter.

Choose Manage Subscriptions.

Click the Add Subscriptions button.

Here you can set up the frequency for how often you want the filter results to be mailed to you.

[Najm Polaris]

@Joey Huang you can see the demo here if there is still any confusion

[Joey Huang]

Oh my gosh didn't even know this existed! This is amazing, thank you both so much @Najm Polaris @Trudy Claspill !!

[Trudy Claspill]

And here is a link to documentation on the topic.

https://support.atlassian.com/jira-software-cloud/docs/work-with-search-results/

[Trudy Claspill]

Hello @Joey Huang 

With a Schedule trigger that includes JQL in the trigger, each action after the trigger will be executed for each issue that is returned by the JQL in the trigger.

In your current setup you should get an email for each issues that your Scheduled JQL is finding. To include information in the email about the issue, use smart values. For instance if you include the smart value {{issue.key}} in the body of the email it will print the issue key in the email.

If you want just one email that lists all the issues found, then you need to pull the JQL out of the Schedule trigger and add a Lookup Issues action to get the list of issues. That same references shows the smart values you can add to the email content to have the complete list of retrieved issues printed in one email.

[Joey Huang]

Not sure how to link old related posts but this was as close as I got https://community.atlassian.com/t5/Jira-Software-questions/Create-an-alert-automation-when-ticket-stuck-in-a-column/qaq-p/1874653?utm_campaign=mentions_reply&utm_content=post&utm_medium=email&utm_source=atlcomm#U2307876