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

Opsgenie and JSM integration

Hello Community,


Need some help in this topic below, 


Our use case is receiving monitoring alarams from various monitoring tools via API or Email and we were routing each monitoring alert to a JSM project and it created a ticket, but without any correlation/dedup and other basic alert tool capabilities we were flooded by alerts. 

Recently after JSM announced new features like Incidents and alerts on our JSM instance we enabled the features and now I have routed all the monitoring alerts to reach Opsgenie and it inturn creates an Incident in my JSM project. Ever since I've enabled this OG has deduplicated 81% alerts which is a good improvement for us. However, this has now introduced new issues for us, as each time an Incident is created in JSM no matter it's triggered from OG integration or an Incident submitted via portal, we see a notification saying 'update this incident' to use all the features this is because the incident is created before new features were enabled, but this is incorrect and seems illogical.

As both of these tools OG and JSM are under the same cloud account for us, our expectation was the alerts creating incidents in JSM will auto link and talk to each other but it's painful that you need to update the incident and link alerts. Also this is causing slowness and Incidents which have no relevance with OG and created after the features enabled are also asking to update everytime! 

1 answer

1 vote
Muhammad Zeeshan
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 12, 2021

Hey Wasim,

Thank you for your feedback and your query! As for the linking of alerts to the Jira Service Management ticket, that was a feature created separately from the Jira Service Management ITSM features; it was an Opsgenie feature to manually link your Jira/JSM issues to your Alerts/Incidents within Opsgenie and vice versa. As you stated, we currently do not have the functionality to automatically link those alerts with those tickets and we do have a Feature Request for such functionality on our internal backlog.

The only automated connection that you can achieve so far is that between an Opsgenie Incident and a Jira Service Management Major Incident; that is the port of the new Jira Service Management ITSM Feature set.

Hope this helps and please feel free to reach out to Opsgenie or Jira Service Management Support for detailed queries and personal issue investigation via:

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events