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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,463,074
Community Members
 
Community Events
176
Community Groups

Double OpsGenie Alert

We found it weird that all our Alert were entering with the subject "Incident Raised"

 

Then we create a webhook and Alert now have the ticket summary, but we still have the Incident raised alert. So we now have 2 alert for the same ticket. How do I stop the incident raised alert?

 

Any help would be appreciate :-)

 

opsgenie.png

2 answers

1 accepted

1 vote
Answer accepted

For anyone else that runs across this issue, its because the Responder Alerts are enabled in your Incident Management section of your JSM portal. You need to either use the integrated OpsGenie alert and set up your affeted services to point to the proper team in Jira, or disable it and create your own custom integration via triggers in OpsGenie

0 votes
Nick H Atlassian Team Mar 16, 2022

Hi @Steve Fournier ,

Looks like that "Incident Raised" alert triggered the creation of an incident - which means there must be some Incident Rule automating the creation of an incident through the JSM issue. You should be able to click into alert #117 to see how that incident was triggered.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS

Atlassian Community Events