| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Overview
A filter is a set condition. Many features of Jira Service Management use filters to provide action execution based on some conditions. You can customize to process integration actions with certain incoming data, fire callbacks for particular types of alerts, apply policies to certain alerts, and do a lot more.
For example, Jira Service Management processes all incoming data from integrations, and then it checks them against your integration's actions for execution. Integration actions have a processing order. At most one action can execute on a single webhook. A filter has a condition set. If the first action's alert filter does not match the incoming webhook data, Jira Service Management moves to the next action in line. It then evaluates this action's alert filter. If an action's alert filter matches the data, Jira Service Management executes that action. Then it ends the processing of that particular webhook. If it finds no matching action, nothing happens. In an action’s alert filter, if the condition match type is set to “Only alerts that match any condition”, then in the incoming data if the variable ‘Status Message is equal to ‘Failed' or 'Still Failing', then Jira Service Management creates an alert according to the setup specified in the alert fields. The processing ends there. But if the incoming data with 'Status Message' equal to something other than these comes to Jira Service Management, it checks it against the 'Create alert’ action. When that doesn't match, the next filter of the 'Close alert’ is processed.
...
Select + Add condition to add more conditions or X icon to delete them.
Condition operations
Equals: Applicable to string, boolean, and number variable types. It returns true if the specified variable's value and the expected value are the same.
...
Equals ignore whitespace: Applicable to string type. It returns true if the specified variable is equal to the expected value after removing all whitespace(space, tab, new line, carriage return characters) from both the specified and the expected value.
Alert properties
For any action set up for an integration, you must define an Alias and match it exactly in order for the action to be executed. An Alias is a user-defined unique identifier for "open" alerts. Also used in de-duplication, you cannot save the integrations if the Alias field is left empty nor are the actions functional.