Watch Using notification rules on Youtube.
Notification rules are used to configure You set a notification rule when you want to control how you are notified either based on the content of an alert or the time of the day. You can also update the rules with a series of options - turn them off/on, apply time restrictions, or edit the contact details/order.
Configure conditions, time constraints, and notification steps for an event for each notification action type. There Following are 8 a few types of notification events within Opsgenieevents in Jira Service Management that you can set up personal notifications for:
New Alertalert: A new An alert is created for which you are added as 're a recipient. Any contact method you add automatically reflects in this rule type by default.
Acknowledged Alertalert: Another user member on the team has acknowledged an alert that you were notified of.
Closed Alertalert: Another user member on the team has closed an alert that you were notified of.
Re-Notified Alert: An alert for which you were notified previously notifies you again via an escalation rule or auto-restart configuration.
Assigned AlertAssigned alert: You were assigned as the owner of an alert by another usermember.
Added Note to Alertadded: Another user member added a note to an alert that you were notified of.
Schedule Startstart: Your on-call rotation is being startedabout to start.
Schedule Endend: Your on-call rotation is being ended.
Incoming Call Routing: A new incoming call has been received and you're on the call recipients list.
...
about to end.
You can add as many notification rules as desired for each event.
...
| Info |
|---|
...
Customising notification rules isn’t possible in the Free or Essentials plans for Jira Service Management. You can configure only one rule per event (such as new alert, schedule start, etc). |
...
To add a notification rule:
Select the plus (icon) icon along the event name card.
Select an event from the Rule type dropdown.
Enter a title for the rule in Rule title.
In the Notify me section, select one of the three options:
All the alerts (no conditions in use): No conditions are set. The notification rule is applied to all the alerts.
Only alerts that match any condition: The rule is applied to only those alerts that match any of the conditions you set.
Only alerts that match all the conditions: The rule is applied to only those alerts that match ALL the conditions you set. If the matching fails even for one condition, those alerts are excluded.
If option (b) or (c) is selected, you need to specify a set of conditions:
...
Select + Add condition to add more conditions or the cross sign to remove them. Every condition you add comprises the following elements:
The alert parameter that needs to be evaluated and its key (if applicable)
The clause of 'Is' or 'Is Not'
The functional operation that the parameter is expected to comply (changes according to the type of the variable)
The value of the parameter selected
The changes you make are applied only after you save them and the rules work only after you turn them on. You can also drag and drop any rule to change the order.
It’s important to pay attention to the order of the notification rules within the same event type. While configuring a notification step If you’ve added multiple rules for a given notification rule– specify the contact methods used and the delay between the event and notification. Adding multiple notification steps is allowed for the same notification rule without any limitation. Furthermore, enable the Repeat option of a notification rule for some event types to notify in a loop event, only the first notification rule whose conditions and time constraints (if any) perfectly match is applied. The rest of the rules that follow it are ignored.
...
Specify the contact methods to use for every notification rule in the Via section. For the “New alert” type, you can also receive repeated reminders for the event by selecting Get repeated notifications for this rule and specifying a duration with a maximum of 10 times (as long as the details of the concerned alert in question aren't opened.
...
Please note that the repeating starts when the defined time threshold is passed after the execution of last notification step. For example, if an event occurs on 16:00; considering the configuration of the notification steps above, the user is notified at:
16:00 (iPhone)
16:01 (iPhone)
16:02 (Voice)
16:04 (iPhone)
16:05 (iPhone)
16:06 (Voice)
16:08 (iPhone)
and so on.