Alert ownership for multiple teams/owners

[Angelodaniel]

Problem Statement

Imagine there is a monorepo, and its main "project" has multiple shared-ownership teams.

The Sentry project has 4 "project teams" assigned, but as the alerts can only have a single person or team as the owner the other teams of that project cannot edit the alert.

It would be great if the alerts either a) shared/inherited the project owners or b) could also have multiple owning teams.

Solution Brainstorm

All or nothing solution: by setting no owner of the alert. Everyone has access to it. - This is nice, but does not give the granular control like with multiple owners.

┆Issue is synchronized with this Jira Improvement by Unito

[getsantry]

Assigning to @getsentry/support for routing, due by Tuesday, February 21st at 11:17 (yyz). ⏲️

[getsantry]

Routing to @getsentry/workflow for triage, due by Wednesday, February 22nd at 5:00 pm (sfo). ⏲️

[brianthi]

Hi @Angelodaniel, thanks for the feedback. I've backlogged this request for now and shared it with our PM.

[therealarkin]

Thank you for sharing this feedback about the limitations of the current alerts system. I see two possible directions for addressing this issue:
a) "Simplicity": We can improve the intelligence of our notification system by automatically assigning alert ownership to the relevant teams based on the affected code or service. This would reduce the need for manual intervention and make the system more user-friendly.
b) "Power": We could also introduce the ability to assign multiple teams or shared ownership. However, we should be mindful that these features may only be adopted by a small percentage of users, and may add unnecessary complexity for others.

Good topic for backlog for Q2 and decide on a direction.

@Angelodaniel - do you mind sharing some accounts (in a private google sheet, or something), that this is requested for?