Engineering and IT automations
Decide about the work that has been open for a month
Asks Jira monthly for issues open longer than 30 days and emails you the list to close, defer or do.
Add this automation
Free, and no card. It runs for real, five times.
What it does on a run
- 1Ask Jira what has been open a long time
- 2Make the backlog decidable rather than long
- 3Email me a list I can actually work through
When it runs
Every month on the 1st. You can change the schedule in plain words after you start it.
What it needs
JiraGmailConnected once, then reused by every automation that needs them.
What you fill in
Asked once, on the review screen, before it runs for the first time. Everything else it works out for itself.
- Jira project key (for example ENG)required
- Send the list tooptional
Where it stops
It halts before the irreversible part and shows you what it is about to do. You see the message, the recipient and the data it read, and nothing is sent until you say so. Once you trust it, you can tell it to stop asking.
Free, and no card. It runs for real, five times.
Automations like this one
All 10 in Engineering and IT- Read the bugs that came in this weekCollects the Jira bugs raised in the last seven days and emails you them grouped by what they touch.
- Surface the work that is blockedAsks Jira each morning for issues flagged blocked and posts them to Slack with how long they have been stuck.
- Write the on-call handoverReads what was raised and what moved in Jira over the last day and posts a handover note to Slack.
- Draft the release notes from what shippedReads everything Jira moved to Done in the last week and files a draft set of release notes in Notion.
- Find the sprint work that has stopped movingAsks Jira each morning for open sprint tickets untouched for three days and posts them to Slack.
- Sweep up the issues nobody ownsAsks Jira each morning for open issues with no assignee and posts them to Slack to be picked up.