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

Not receiving alerts from Jira Service Management

Hi, this is a pretty wide open question, but all of the sudden I am not able to receive JSM/ Service Desk Tickets into Opsgenie for one of our teams.

I've went so much as to create a new JSM integration and no luck. 

I've checked the logs and see [incoming][jira-software-cloud]Received integration question with event ID... but there is no data in the logs.

I also see other successful integrations for other teams occurring around this integration.

Any thoughts?  We have 14ish teams in Opsgenie that are connecting back to JSM.  I'm wondering if there is a limit?

I discovered this in trouble shooting a weird thing where the 'priority' of JSM wasn't setting the Opsgenie priority field.  It does that by default in other integrations as well. 

2 answers

1 accepted

1 vote
Answer accepted
Nick H
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Mar 24, 2021

Hi @Chris ,

This is pretty wide open without being able to dive into the account and review the logs.

But you did mention - "I've checked the logs and see other successful integrations for other teams occurring around this integration."


This log: [incoming][jira-software-cloud]Received integration request - all leads me to believe that the JSM alerts might be deduplicating under one alert. 

Our documentation explains there should be a webhook configured in JSM for each integration:

But if you have multiple integrations / webhooks - you should consider configuring a JQL within each webhook to specify when they trigger.

For example:



If no JQL is configured under multiple webhooks, they would all trigger, and only one Opsgenie alert would be created with an increased alert count since their aliases would match - aka they'd be deduplicated:

^ If this is not the case, I'd suggest searching the Opsgenie logs for the issue number to troubleshoot. If Opsgenie is receiving the requests, it'll be logged (even if there are errors). If there are no logs, Opsgenie is most likely not receiving the request and there is probably a slight misconfiguration on the JSM side.



Hope this helps! Let us know if you have any additional questions, issues, etc.

Thank you Nick, I updated the JIRA to reference the project key and not the name.  But I'm back to my original issue where the JSM priority won't seem to update the opsgenie priority for this specific integration. 

Nick H
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Mar 24, 2021

This similar community post should help with mapping priority:

Since JSM priorities do not match with Opsgenie's out-of-the-box, multiple Create Alert actions that filter on the JSM priority can be added to map to the corresponding Opsgenie priority.


But - I do see that your priority includes a number that corresponds with Opsgenie's priority; JSM Highest (P1) ~ Opsgenie P1.

If all of your priorities do correspond with a number similar to Opsgenie, you could instead use one Create Alert action, and use the Custom Value to Opsgenie Priority mapping with an expression like this: {{priority.extract(/P[1-5]/)}}



I adjusted my JSM priorities to something similar, ran a few tests, and was able to use the configuration above to work as expected. Below are screenshots of both:




Hope this helps!! Let us know if you have any other questions, issues, etc.

Wrong field, sorry

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events