• Products
  • Get started
  • Documentation
  • Resources

Work with alert filters

The feature described in this article is currently rolling out to some Jira Service Management Cloud customers. It may not yet be visible or available on your site.

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 alert filter does not match the incoming webhook data, Jira Service Management moves to the next action in line. It then evaluates this alert filter. If an 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 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.

Jira Service Management provides default actions with pre-configured filters and alert fields for every integration. You can customize them the way you like - you can edit them, delete them, or add new actions of your own.

There are three types of 'condition match' you can select from:

  • All the alerts (no conditions in use): The integration action matches every data that's evaluated against it and executes the action. You don't need to specify any condition.

  • Only alerts that match any condition: If even one of the conditions specified in the condition set matches the incoming data, Jira Service Management executes the action.

  • Only alerts that match all the conditions: The webhook data has to match every specified condition in the condition set. If any of them fails, the action isn't executed. Jira Service Management moves on to process the next integration action, if there is any.

If you select either option with conditions, specify a list of conditions for evaluation.

An image showing the alert filter
  • The variable in the specific integration's webhook data to evaluate.

  • The clause of 'Is' or 'Is Not'

  • The functional operation that the variable is expected to comply. The set of operations you can select from changes according to the type of the variable.

  • The value of the variable.

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.

Contains: Applicable to string, list, and map types. It returns true if the specified variable's value contains the expected string. For maps, the expected value can be contained by key or by value fields.

Is empty: Applicable to string, list, and map types. It returns true if the specified variable is empty. For string, it checks character count, for list and map, it checks the size.

Matches (Regex): Applicable to string, list, and number types.

  • For string and number types, it returns true if the specified value matches the given regular expression.

  • For list types, it returns true if any of the given values matches the given regular expression.

Regex match operations has 10 seconds timeout limit. If it takes more than 10 seconds, it returns false.

Contains key: Applicable to map type. It returns true if the specified variable contains the expected value in keys.

Contains value: Applicable to map type. It returns true if the specified variable contains the expected value in values.

Starts with: Applicable to string type. It returns true if the specified variable starts with the expected value.

Ends with: Applicable to string type. It returns true if the specified variable ends with the expected value.

Greater than: It is applicable for Number type. It returns true if the specified variable is greater than the expected value.

Less than: Applicable to number type. It returns true if the specified variable is less than the expected value.

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.

Additional Help