Extend capabilities for configuring slack notification triggers to give more control of channels to notify

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Problem to solve

The configuration for slack notifications lacks the ability to dynamically route to channels based on details of the trigger.

For example, when a notification is triggered on a merge of a branch, depending on the name of the branch, I might want to notify a different slack channel.

i.e.

feature/search branch might only need to notify #search-team

feature/inventory branch might only want to notify #inventory-changes

Intended users

Further details

Cross functional teams Cross functional teams often use a single slack channel. We want the ability to notify when an update has been released to everybody involved in that channel.

Reduced noise Right now, we only have capability for a single repository to notify on everybody contributing to that repository. With a repository that has a lot of contributors, this is very noisy. Much easier to be able to route changes to where it makes sense.

Proposal

A potential path to providing this capability would involve the following

1. Allow Multiple Trigger Configurations Based on the next bullet point, if we had more granular control of how we could configure triggers, then we would need the ability to specify more than one of these.
2. Add Qualification/Matching on Trigger Criteria This could be in the form of a regex potentially. Ultimately, when evaluated, if the criteria evaluates to true, that configuration can be used. i.e. A search team might have it's own configuration for the Deployment trigger that matches on feature/search whereas the inventory team might use the criteria feature/inventory. Both pointing at respective channels.

Permissions and Security

Should be consistent with existing permissions.

Documentation

• Update Docs

Availability & Testing

What does success look like, and how can we measure that?

Acceptance Criteria

• A user can route a slack notification to a specific channel based on basic details available. Included, but not limited to branch name, repo name, trigger name.

Success Metrics

• General increase in the use of slack notifications. Right now, it likely is limiting the use of this because of the inability to segment on notification triggers.

What is the type of buyer?

Members of a cross-functional team?

Customer Impact

• Ultimate, SaaS, 140 seats