Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

alerts for high priority issues created in service desk

I'm pretty new to using service desk and we don't get a huge number of help desk issues

But any suggestions on ways to create alerts when issues are created with Highest priority to ensure we triage it asap.. 



4 answers

1 vote
Jack Community Leader Nov 20, 2018

here are some things to consider:

  1. Add SLAs to your issues based upon priorities
  2. Use Automation to notify certain users based upon priority
  3. Consider Escalation methods

this is a good read on configuring notifications

Hi @Ann Marie Kjerland -

There are automation rules that you can use for your requirement. Service Desk has some preset automation rules that you can use out-of-the-box or edit them to suit your requirement, if you will. You can also create custom automation rules to meet your requirement(s).

I am not sure if you have already reviewed this documentation that covers the scope the topic you are looking for - This document refers to a preset rule template 'Urgent issue alert" that may help you in accomplishing what you trying to do here.


Additionally, if you would like to bring alerts to yourself or your team, outside of email notifications, you could also explore pagerduty integration with JIRA (

Hope this helps!



1. Go to SLA and write in JQL priority = Highest  then in Goal write for ex. 1m (which is 1 minute) and choose your calendar.

2.Save the SLA with any name you prefer, for ex. "High Priority"

3. Go to Automation and create a Custom rule in this way: When should be SLA time remaining and choose your SLA (High Priority in the example) and in the Event choose Breached, you can leave IF empty if you want this rule to work for all issue types and in Then choose Alert user, save it and in this way you will be notified after a minute when a highest priority issue is created


I'm new to JIRA SD, more user than administrator, so better I'd like to ask professionals :) 

We have a rule: When this happens = issue created; If these match = Priority = Blocker, Then do this = Alert Jira users. It means that if blocker is created, users get message. 

But we have a doubt about "created".

In our system when Ticket is created it's get status Registered. Could it be, that alert message is sent only when status is changed from Registered to Waiting for support or Analysis? 

Thank you in advance!

Jack Community Leader Jun 10, 2021

Hi @Žydrunė Stonkuvienė , This really should be a new question. With that said, if you have an automation rule as you described then the alert message should go out to the defined users anytime an issue is created regardless of the status. Are you saying that the alert is not being sent to these users but anyway she was created? If so please add a screenshot of your automation.

Thank's for quick answer!

We have a delay in receiving the message, I am wondering if it possible that the status matters because according to the rule described, it should not. 

The rule is very simple:


Of course we will test it once more, but it will be useful to know if any other circumstances or settings may affect. JIRA has so many functions and possibilities for configuration, it's not easy to understand quickly :)

Jack Community Leader Jun 10, 2021

I see nothing wrong with your rule. If it is just a matter of a delay that could be due to other issues. If you’re still getting notifications, and you should, then I would not be concerned about it.

Like Žydrunė Stonkuvienė likes this

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

274 views 8 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you