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

JSM integration for edit issue not working

So I have configured my JSM integration on the Ops Genie side (under my team integrations) and on the JSM side by creating a web hook.  I configured the web hook to trigger on issue creation or issue update.

The integration works great when I create a new issue that meets the criteria, but when I edit an issue I see a warning in the log and an alert is not created.

The payload for create issue and edit issue are the same except the webhook event field.

      "webhookEvent": "jira:issue_created",


      "webhookEvent": "jira:issue_updated",


The error is

[JiraServiceDesk-GIAS_Jira Service Management] Skipping incomingData, no matching actions found


Why is it not working for issue_updated?  Where are these 'actions' defined such that no matching ones were found?  The Jira Service Management to OpsGenie side of the integration setup has just the field for API Key.


2 answers

1 vote
Nick H
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Dec 10, 2021

Hi @Lewis Martins ,

These actions can be defined under the integration's Advanced tab. Note this tab is only available on the Standard and Enterprise plans:



Here is where you can control what will happen to the Opsgenie alert when the JSM issue is updated, such as create an alert, ack it, etc. Examples:



Hope that helps! Let us know if you have any other questions.

So I don't have an advance tab, which I guess means we are not on the standard plan.


Is it expected that issue_update does not work on the lower plan?

Oh and we are on Standard plan of JSM.  I don't see anywhere to manage the OpsGenie plan as it only shows up as a free app and isn't under 'manage subscriptions'

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

The JSM Standard plan is the equivalent of the standalone Opsgenie Essentials plan - which does not include the advanced tab on integrations. You'd need to be subscribed to JSM Premium or JSM Enterprise for this functionality.

Out of the box and by default, the integration is not mapped to do anything when an issue is updated. This needs to be configured on the Opsgenie side if your plan offers it.

So unfortunately I don't think it'd be possible with your use case since this isn't offered, and the automation rule is happening after the alert is created. 

Like Howard Nedd likes this

Hello Lewis,

We did the same setup. Some clarifications:
1. Have you configured anything else in the Filter and Alerts Fields section in Opsgenie? Those right after the Settings section?

2. What type of Opsgenie alerts you plan to use?

3. Any specific jira issue field you updated and wanted(included in the payload) to reflect in Opsgenie side?

In my experience, you may configure either creating an alert, closing or acknowledging an alert in opsgenie depending on your desired action or behavior.

All I really want to do is alert the on call person when a high priority issue is created after hours.

To do so, I have setup a team and the integration with JSM.  Unfortunately, one piece of info we need to route the alert to the correct team is set in a JSM automation (on create, but technically takes place after creation) so the filter does not pick it up with issue creation. 


I understand. Thanks for sharing. If this applies, you may use the trigger field value changed and then try using the assign alert API if the jira ticket assignee is what's updated from jira. (found in this documentation)

Use the API key from Opsgenie and the URL for POST method.{{alias}}/assign

payload will include detail body like this: (see documentation for actual formatting)

I don't think you need the webhook event name.
See if that works.

Thanks.  I did get the alert API working, though I haven't tried assigning it to particular member.  The field that gets updates lets us know the group/team responsible for the issue.  However, if it is off hours we don't want to bother the entire team, just the person on call.


If the API allows, I will see if I can get the oncall person from the team and send them an alert all from our JSM automation that sets the group/team responsible.

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

Seems like you could manage that - only notifying the on-call user(s) during off hours - under a team's On-call tab.

Routing rules can be restricted to times, or days/times - such as after hours - and have alerts created during these times send only to the team's on-call schedule:



Like # people like this

Thanks Nick!  I wrote an API script to get the team's on call person and then create an alert where they are notified but it is visible to team.

This seems to do same thing, but much easier!

Like Nick H likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events