How Do i send an email to assignee when the due date is reached?

[Nag]

Is there a way to remind assignee about the following via e-mail?

• Tickets being due within the next 24 hours
• Overdue tickets

We have installed Automation Lite for Jira.

Jira Version 7.6.

[Mikael Sandberg]

Automation Lite does not allow you send out email to the assignee, you would need the regular/pro version to do that. We used to just add a comment in the issue when it was overdue before we decided to go with the paid version of Automation.

[Max Foerster - K15t]

Hi Redy,

have you ever thought about using the built-in mechanism of group filter subscriptions in Jira? Both of your requirements can be made into JQL queries in combination with currentUser and so you could set up a subscription sending notifications to everyone (if the query returns results) every workday in the morning. 

Of course tools like Automation for Jira, Automation Toolbox for Jira or AutoBlocks for Jira offer more features to sent more appealing notifications.

Best, Max

[Nag]

Hi Max,

Thanks for the quick response.

I have tried subscribing JQL filter, how ever it allows only personal or Jira groups.

I'm not sure how to set up to assignee of the issue or any particular project role. Please advise.

Thanks!  

[Max Foerster - K15t]

Hey,

yes, that's true only groups and individual users. There's no other way with group filter subscriptions. So the easiest way would be to simply choose the group that grants users access to the application (e.g. jira-software-users). But then everyone would be notified about upcoming due dates. If you need a smaller group of recipients you would have to create that group and add members to it.

For a more advanced approach, you will have to look at for example the available apps I mentioned above. Everything that enables you to schedule the execution of a certain rule (with narrowing down the scope, conditions, the usual stuff 😁) and sends meaningful notifications.

[Mikael Sandberg]

You should be careful assigning the application group to a JQL subscription, it can have a performance impacts on your system. It is always better to make the subscription as narrow as possible.

[Max Foerster - K15t]

I'm with you Mikael. I would also try to avoid this by all means. It's more like the bare minimum solution. But you wouldn't use this on a filter returning all issues of your instance and not in an enterprise-sized instance. So this can be a viable solution depending on a few factors like your deployment size etc..