Issue Owners

The Issue Owners feature allows you to reduce noise by directing notifications to specific teams or users based on a path or URL. This allows you to get issues into the hands of the person who can fix them, faster.

How It Works

Issue owners builds upon your alert rules to specify who to notify about a given issue.

In your group settings, you will define which users or teams own which paths or URLs for review. When an incident happens that triggers an alert, Airlock evaluates whether the incident’s URL tag matches the URL you specified, or if the path you specified matches any of the paths in the incident’s events.

If there is a match, only Owners will receive the alert for the incident. By default, if there is no match, the alert will be sent to all members of teams associated with this group. You can also choose to specify that in the case of no match, no users be notified, by toggling off the switch in Group Settings > Issue Owners > ‘If ownership cannot be determined for an issue…’

At this time, the Issue Owners feature is only available for email notifications. This means that your alert rules must trigger email notifications to be affected by your Issue Owners’ rules.

Configuration

Adding a New Rule

To configure Issue Owners, navigate to your Group Settings > Issue Owners. To add a new rule, you can use the dropdown to specify whether you’re using a path or URL. Then add the path or URL, and specify which users or teams own that path. You can add multiple users or teams to one path.

You can also use the text editor below to manually add rules.

You can also add a new rule from an individual issue. From the issue details, click the ‘Create Ownership Rule’ on the right-hand panel.

In the resulting modal, you’ll see the paths and URLs connected to the issue, and can either select one to build a rule off of, or create your own rule.

Syntax

Issue Owner rules use the following structure:

type:glob owner

type can be either path or url, depending on whether you’re specifying a path or URL.

glob will be the path or URL you are specifying (for example, src/javascript/* or https://www.example.io/checkout. You can use the * character to match everything, or the ? character to match any single character. This feature does not support regex.

owner can be the email of an Airlock user, or the name of a team, prefaced with # (i.e., #backend-team). To list multiple owners of the same path or URL, place them on the same line like so:

type:glob owner1 owner2 owner3

Teams and users must have access to the group to become owners. To grant a team access to a group, navigate to Group Settings > Group Teams, and click ‘Add Team to [Group]’. To grant a user access to a group, the user must be a member of a team with access to the group. To add a user to a group’s team, navigate to Group Settings > Group Teams, select a team, then click ‘Add Member.’

Troubleshooting

  • Make sure that all teams and users have access to the group; if they do not have the correct access, the Issue Owners rules will fail to save. To grant a team access to a group, navigate to Group Settings > Group Teams, and click ‘Add Team to [Group]’. To grant a user access to a group, the user must be a member of a team with access to the group. To add a user to a group’s team, navigate to Group Settings > Group Teams, select a team, then click ‘Add Member.’
  • Make sure that alert rules are configured to send email. First, check to see that the Mail plugin is enabled by navigating to Group Settings > Integrations. Then, navigate to Group Settings > Alerts > Rules, and confirm that notifications are being sent to Mail or to ‘all enabled legacy services.’