Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Need info to create automation

Hi Team,

In JIRA Software project I am trying to create automation rule for SLA breach, wherein remainder should be sent to a particular group before 1 day of SLA as email notification and also comment in the ticket.



Dinesh V

3 answers


Jira's automation has some limits for the execution, so if you have the Standard package, you won't be able to automate much there. The community leader answered this question in more detail here → Jira Automation, usage limits 

I would like to recommend the SLA Time and Report for Jira add-on. Here you will be able to set up your custom notifications for breached or exceeded SLA for any assignees and groups in comments to issues (+email) or on the SLACK channel.2022-11-30_17-28-04.png

You can use the 30-day trial to test the add-on yourself.
This app was developed by our company, so if you require supplemental information, please contact me, I will be happy to assist you.


SLA configuration is rather a feature of Jira Service Management and better supported there, in the sense that it's easier there to use the SLA timer to select issues that are ablout to breach. In Jira Software, you could mainly use the due date (or another date custom field) as a target for issues to be delivered on time.

Having said that, the principles for your automation would still remain the same. The rule might look somewhat like this:

Screenshot 2022-11-29 at 19.27.30.png

In the trigger, you should specify a JQL filter to retrieve the issues that are about to breach the SLA in a day. Using the due date, that might look like this:

resolution = unresolved and due <= endofday(1)

this will fetch all issues with a due date before tomorrow 23:59 (more or less) that are still open. Be aware that if the issue will not be fixed before 9 AM on the next day, the email and comment will be added once more (and again) until the issue gets resolved.

Hope this helps!

1 vote
Mark Segall Community Leader Nov 29, 2022

Hi @DINESH - Since you're on a software project, I'm assuming that "SLA" actually refers to a due date of some kind?

Assuming you're using Due Date to capture this info, you could set up automation like this:

  • TRIGGER: Scheduled (Daily)
    • statusCategory != Done AND dueDate < 1d AND dueDate > startOfDay()
  • ACTION: Add Comment
  • ACTION: Send Email

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events