Notification grouping / digests

When does event grouping apply for a notification scheme?

Event grouping is only applicable for notification whose trigger is native Jira webhook event:

• Issue Created

• Issue Updated

• Issue Deleted

• Comment Created

• Comment Updated

• Worklog Created

• Worklog Updated

Pseudo events are also allowed:

• Issue Resolved

• Issue Assigned

• Issue Moved

• Issue Closed

• Issue Reopened

• Field Updated

Configuring event grouping

Open

• Maximum wait time:

  • The maximum wait time in minutes in which events are grouped. Must be between 3 minutes to 20 minutes.

• Maximum inactivity time:

  • If there is no new event within this time frame since the last event then the group will be closed and a notification will be sent to user even if the window time is still open.

  • It is NOT configurable. Hardcoded to 3 minutes just like Jira’s native implementation.

Factors which contribute to grouping logic

Events are grouped into the same group if they have the same:

• Event type (see above)

• Notification ID (groupings don’t happen across multiple configured Notifications)

• Recipient(s)

• Issue ID (only if the configured Template does NOT contain issue table block)

Template to be used for digest email notification

It is depends on the template configured on notification settings:

• If dynamic template is used then:

  • Comment template will be used if all events in group are comment events

  • Single issue template will be used if all events in group are from the same issue

  • Table issue template will be used if events in group are from various issues.

• If specific template is configured then it will be used directly.