...
You can further make advanced settings in the integration to cover a variety of alert scenarios. These scenarios are called "actions" and they specify how and when alerts can be created, closed, acknowledged, etc. Jira Service Management offers default actions for every integration, but you can customize them or add as many actions of your own as you like. For example, you can have three ‘Create alert’ actions; which means the webhook data that comes to Jira Service Management is evaluated against these three scenarios in order, and if any one rule you set matches, a new alert is created.
Action processing
There is a specific order in which the actions are evaluated. For example, ‘Ignore’ actions are evaluated first by design, and ‘Add note’ actions, last. This means the incoming data is evaluated against ‘Ignore’ actions and if one of them has a match, then no further actions are evaluated; only that Ignore action gets processed.
...
| Info |
|---|
You can have up to 255 actions for each integration, up to 250 rules for the incoming part, and up to 50 for the outgoing. |
Changing the order of actions
The actions of the same type also are evaluated in order and you can change it. For example, you have three 'Create alert' actions in the order of CreateAlert1, CreateAlert2, and CreateAlert3. You can just drag CreateAlert3 and move it up to change the order to CreateAlert3, CreateAlert1, and CreateAlert2. Now upon saving the rules, CreateAlert3 is evaluated before the other two against the incoming data. If the filter for CreateAlert3 has a match, CreateAlert1 and CreateAlert2 are evaluated. Remember that for one incoming request, only one action is run.