Configure alert grouping

Alert grouping lets you control how alerts are grouped in Jira Service Management. By defining grouping rules, you can reduce alert noise and make sure related alerts are organized in a way that matches how your team triages and responds to incidents.

Access alert grouping settings

You can configure alert grouping in either of the following ways:

1. Go to Operations.

2. Select the team you want to configure alert groups for.

3. Open Alert groups.

How alert grouping works

Alert grouping determines which alerts are considered related and grouped together based on:

• a grouping window (time-based)

• selected alert fields (attribute-based)

Alerts that match the configured criteria within the selected time window are grouped together automatically.

Grouping window

The grouping window defines how long incoming alerts are considered eligible to be grouped together.

Group by

Use Group by to choose which alert fields must match for alerts to be grouped together.

You can group alerts by one or more of the following fields:

• Alert title (Mandatory field)

• Alert description (Mandatory field)

• Affected services

• Integrations

• Tags

• Sources

• Priority

Alerts are grouped only when all selected fields match within the grouping window.

How is usage calculated for alert grouping

Alert grouping uses Rovo credits when you take certain actions on alert groups or on selected alerts within a group. Each billable action includes a per user, monthly Rovo credit allowance of 100 credits.

What counts as a billable action?

For alerts

When an alert group is selected, the following actions are billed:

• Close all

• Acknowledge all

• Delete all

• Create incident

• Assign to me

• Assign

• Link incident

• Snooze All

• Snooze

• Classify an alert group as Signal or Noise

For alerts within a group

When an alert within a group is selected, the following actions are billed:

• Close

• Acknowledge

• Delete

• Create incident

• Assign to me

• Assign

• Link incident

• Add tag

• Add note

• Add responder

• Classify an alert as Signal or Noise

What doesn’t count as a billable action?

These actions are free to use:

• Update Signal and Noise (SnR)

• Remove alert from group

• Expand Alert group

What to expect if you go over your credit allowance

Organization and billing admins set Rovo credit usage limits and have controls to adjust limits as needed. When you reach your usage limit with extra usage enabled, billable actions continue without interruption. Admins are notified at 80% and 100% usage, and extra usage is charged on your next invoice. See Manage extra usage

If extra usage is disabled, you won’t be able to take billable actions on alert groups or selected alerts within a group until credit allowance resets on the first of the following month. Free actions will continue to work.

If you need to use more than your total allowance, you can also consider purchasing usage packs.

Organization admins can track Rovo credit usage in Atlassian Administration.

To view your usage:

1. Go to Atlassian Administration. Select your organization if you have more than one.

2. Select Insights, then Platform usage.

3. From here, you can view your total credit allowance, current usage, app-level trends, user-level usage, and which features are consuming credits.