Work with advanced settings

https://support.atlassian.com/opsgenie/docs/use-advanced-integration-settings/

Jira Service Management integrations may have two types of settings: Basic and Advanced. You'll find basic settings on the main screen of an integration.

With the advanced integration settings, you get the most customizations for alerting . You can define when the system should create an alert, execute a close action, automatically acknowledge an alert, or add a note. The framework also enables you to parse out anything from your webhook data and use it dynamically to build your alert content.

The rules execute in top-down order. The first matching rule will execute first and it stops evaluating further rules. Learn more about integration types and actions.

You’ll find the rules (Ignore, Create Alert, Close Alert, Add Note) in Advanced settings, under the Actions title. The rules are responsible for the action processing. Every time data lands on the endpoint (or email box), these rules are matched to the data in top-down order. Each of these rules has a Filter section. The first rule, matching your alert (with a top-down order), will execute the action associated with it. The Alert Fields section provides the details of that action. Your alert will be created according to the template capture in the Alert Fields section.

Action Processing

Integration advanced settings consist of many different alert scenarios. These scenarios are called “Actions” and specify how and when alerts can be created, closed, acknowledged. Jira Service Management provides default actions for every integration. But you can customize them and add as many actions as you like. For example, you can have three Create Alert actions. This means the webhook data that comes to Jira Service Management will be evaluated against these three scenarios in order. If one of them has a match, a new alert will be created.

Action Filters

Every action has a filter section. Jira Service Management processes every incoming data associated with your integration. Then it evaluates them against your integration's actions for execution. Integration actions have a processing order, and a request executes only one action. If the first action's condition set, Filter does not match the incoming payload, Jira Service Management moves on to the next action in line and evaluates its Filter. If an action's Filter matches the data, Jira Service Management executes that action and ends the processing on that particular webhook. If it finds no matching action, nothing happens.

Pre-canned integration has a list of prepared filter options. The most common ones are available, tailored to the integration you choose. Learn more about action filters in integrations.

Also, find out which regular expressions you may use to customize and filter alerts.

Alert Fields

The action executes according to the template and settings you capture here. The figure below shows a Create Alert action's Filter. Its condition match type is set to Match all conditions. If the variable Action in the incoming data is equal to Create and the Source Type Name variable equals Monitor Alert, then a Jira Service Management alert will be created according to the setup specified in the Alert Fields. And the processing will end there.

On the right side, you'll find draggable fields (blue boxes). You'll also see dynamic fields captured in some of the default alert fields (those inside the curly brackets). Using these, Jira Service Management parses your data to construct rich and informative alerts. You can use dynamic fields to customize alert properties. This will automatically parse out a variable from the payload every time you create an alert according to this "Alert Fields" section.

If you don't need the whole variable and need only a part of the data, like a certain part of an email subject, you can use one of the string processing methods.

Learn more about the dynamic fields.

• Replacing OG with JSM
• Basic grammar & spell check
• US English
• Positive language
• Removing passive voice (wherever necessary)
• Simplifying sentences
• Change V&T
• Replacing old links and images with new ones
• Structure of these pages: Do these need to be separate topics? Can it be added /merged with another topic? Does the headline need to revised?
• Conceptual validation: Do these journeys, concepts, terms make sense for JSM? Do we need a developer to verify parts of this content?