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

How to Alert Different Teams Through One Integration

Advanced integration settings are available only on the standalone Opsgenie Standard and Enterprise plans, and the JSM/O Premium and Enterprise plans.


Account Admins and Owners by default will only have permission to global integrations.


When an integration is global - meaning it is assigned to [No Team] - a Responder field will appear within each create alert action. These actions can be configured under the Advanced tab of the integration:



Opsgenie provides default actions for every integration. You can edit these actions, and add others to meet many use cases - such as alerting different teams through one integration + multiple create alert actions.

For example with a JSM integration - filter on the project key (and/or other fields), and add the corresponding Opsgenie team(s) to be notified for specific alerts:



These actions are reviewed in an order of operations from top  down, and only the first matching action will execute. Once this happens, no further rules are evaluated - so order sometimes matters.

Actions follow a simple WHEN/IF/THEN conditional statement; WHEN a request is sent to Opsgenie, and IF the filter’s condition(s) match, THEN have Opsgenie create an alert, close an existing alert, etc.


With the example above if JSM creates an issue under the COMM project, the top create alert will match and notify the Community Team.

If JSM creates an issue under the DEV project, Opsgenie would skip the top action since its filter and conditions do not match the incoming payload. Opsgenie would then review the following create alert action, which would match and notify the Dev Team:



The same idea can be applied to notify multiple teams about one alert as well:




Log in or Sign up to comment
AUG Leaders

Atlassian Community Events