Hi everyone,
I’m trying to figure out how to set up automatic email notifications for our team when Jira issues remain open for a while. Here is what I’m aiming for:
- Send an email to a designated group
- Trigger the alert at 24, 36, or 48 hours after the issue is opened
- Issue only one reminder at the specified time
- Restart the timer if the issue is closed and then reopened
Has anyone implemented something similar? I’m unsure whether this function is built-in or if I need a custom solution. Any advice or suggestions would be greatly appreciated!
Thanks in advance for your help!
I’ve implemented a similar system using Jira’s built-in automation features. It’s quite straightforward once you get the hang of it. The key is to create a custom date field to track when the issue was opened, then set up an automation rule that runs daily. The rule should use JQL to filter for open issues created within your specified timeframe.
One tip: make sure to test thoroughly before rolling it out. I encountered a few hiccups with timezone differences causing some alerts to fire at odd hours. Also, consider the volume of notifications - you might want to start with a longer interval and adjust based on team feedback to avoid alert fatigue.
For reopened issues, you’ll need to add a transition post-function to update your custom date field. This ensures the timer resets appropriately. Good luck with your implementation!
heyy, i’ve dealt with this before! u can use jira’s automation stuff. make a custom date field for when the issue opens, then set up a daily rule. it’ll check for issues open for 24, 36, or 48 hrs and send emails. for reopened stuff, add a post-function to reset the date. watch out for timezone issues tho!
I’ve tackled this issue before using a combination of Jira’s built-in features and a bit of custom scripting. Here’s what worked for us:
We set up a custom field to track the initial open date, then created a scheduled automation rule that runs daily. The rule uses JQL to identify issues open for 24, 36, or 48 hours and triggers email notifications.
For reopened issues, we added a post-function to our workflow that updates the custom field. This resets the timer when an issue is reopened.
One challenge we faced was handling different time zones, as our team is distributed globally. We solved this by standardizing on UTC for all automation timing.
Also, we found it helpful to include direct links to the issues in the email notifications, making it easier for team members to quickly access and address the long-standing tickets.
Remember to fine-tune the notification frequency based on your team’s feedback to avoid alert fatigue while still ensuring timely responses to aging issues.