Send mail when not updated for 3 Days

[Poephouder]

I am trying to make a a Jira Automation, which sends a mail to the assignee, when a issue hasn't been updated for longer then 3 days. (for test purposes it is set on 5 minutes now)

The automation does trigger each 5 minute, but it doesn't send a mail. even though in the JQL in the When: Scheduled i have filled in: 'updated <  -5m'

After that is has a Then: Send Mail to assignee. The issue does have a assignee linked (me)

I cant figure out what I am missing.

[Ben Finn]

Hi @Poephouder I think you should try using the scheduled filter email rather than a automation. These days automations do come at a bit of a price (Meaning you only have a limited amount you can run).

[Ben Finn]

Create a filter with a pretty straightforward query.

Based on my understanding of your requirements, I would suggest something like this:

statuscategory != Done AND updated < -3d

Then save the filter. and where the save button used to be, you should see the word. details. Click on that.

Go to the new subscription section of the pop up, and it should be pretty straightforward from there.

Please let me know if this will work for you

[Dan Breyen]

Hi @Poephouder if you want to do an Automation for this, if you go into Project Settings / Automation and click on the 'Templates' tab.  You'll see a template called 'Resolve issues due to inactivity'.  You should be able to tweak that slightly to get it to check everyday for issues that aren't closed nor updated for 3 days and then add a comment to the ticket (could be internal) which would document it hasn't been looked at, or it could just send an email. You shouldn't need the 'Transition' part.

I'm no Automation expert, but I was able to make a new rule similar to that for my site.

HTH,

[Bill Sheboy]

Hi @Poephouder -- Welcome to the Atlassian Community!

What problem are you trying to solve by doing this?  That is, why do this?

And, what practices does your team normally use to manage work items?

Knowing these things may help the community to offer better suggestions.  For example...

If we assume there is a symptom of work gets "stuck" and so does not appear to make progress, the team may want to raise visibility of that.  There are lots of possible causes to that symptom.  Such as: refinement or planning problems, high work in progress (WIP), trouble focusing on the selected work, skill silos, etc.  Seeing the symptom sooner would lead to a quick team conversation about "why" and help develop experiments to solve it.

Back to practices, if the team regularly has a daily standup, they could check for "stuck" work using a quick filter on the board.  By walking the board from right-to-left (i.e., from Done to Not Started) this symptom would be easy to see and the team can swarm.  This may be more effective than sending an email reminder as that could be missed or ignored.  (Or not sent if an automation rule or filter scheduled does not happen.)

Kind regards,
Bill