getsentry / getsentry/sentry

Option to adjust Scope of GitLab Integration Notifications

Open
#58,462 5 comments 1 reaction 0 assignees View on GitHub
Feature Product Area: Settings - Integrations
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
1d 5h
Merged PRs (30d)
624

Description

### Problem Statement

“It’s currently the case that all notifications to Gitlab are tied to the person who set up the integration. While we know this functionality is working as designed, are you considering adding a way to do the integration via a group or project token?”

”Having the integration tied to the integration master means they get notifications for every Gitlab issue connected to a Sentry error, even if they have nothing to do with them or their team. Notifications can be turned off manually on a ticket-by-ticket basis, but there are circumstances where there are too many to do so, and it still means a flooded inbox from initial notifications, along with confusion about why notifications are received on a ticket people aren’t familiar with or visibly tagged into”

### Solution Brainstorm

Options to assign integration-based notifications to Teams or different users configured within Sentry? Currently it ties to the one who constructed the integration.

### Product Area

Settings - Integrations

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.