Problem Statement
Currently, when setting up an issue alert, one of the available actions is to "Notify Suggested Assignees, Team, or Member." Opting to "Notify Suggested Assignees" prompts Sentry to alert all suggested assignees related to a specific issue that prompted the alert. However, this approach can lead to unnecessary notifications for teams merely suggested as assignees, rather than the actual assignee. This situation is particularly pronounced for errors originating from mobile applications, as they often contain numerous stacktrace items, increasing the likelihood of multiple suggested assignees.
Imagine a scenario where a new or existing issue triggers an alert with the aforementioned action. Teams A, B, and C receive notifications due to being suggested as possible assignees for the issue. After deliberation, the teams collectively determine that team B should take ownership of the issue, marking them as the issue assignee through the Sentry dashboard. Despite this assignment, both team A and team B continue to receive alerts whenever the issue triggers the alert.
Solution Brainstorm
Add another option for this action, like "Send notification to Assignee"
If a specific issue is assigned to a particular team or member, as indicated on the issue details page, Sentry will send a notification to that designated team or member. Alternatively, if the issue has no final assignee like this → 
, we have the option to send notifications to "Suggested Assignees," "Recently Active Members," "All Project Members," or opt for "No One" as a fallback strategy.
Product Area
Alerts
Problem Statement
Currently, when setting up an issue alert, one of the available actions is to "Notify Suggested Assignees, Team, or Member." Opting to "Notify Suggested Assignees" prompts Sentry to alert all suggested assignees related to a specific issue that prompted the alert. However, this approach can lead to unnecessary notifications for teams merely suggested as assignees, rather than the actual assignee. This situation is particularly pronounced for errors originating from mobile applications, as they often contain numerous stacktrace items, increasing the likelihood of multiple suggested assignees.
Imagine a scenario where a new or existing issue triggers an alert with the aforementioned action. Teams A, B, and C receive notifications due to being suggested as possible assignees for the issue. After deliberation, the teams collectively determine that team B should take ownership of the issue, marking them as the issue assignee through the Sentry dashboard. Despite this assignment, both team A and team B continue to receive alerts whenever the issue triggers the alert.
Solution Brainstorm
Add another option for this action, like "Send notification to Assignee"
If a specific issue is assigned to a particular team or member, as indicated on the issue details page, Sentry will send a notification to that designated team or member. Alternatively, if the issue has no final assignee like this →
, we have the option to send notifications to "Suggested Assignees," "Recently Active Members," "All Project Members," or opt for "No One" as a fallback strategy.
Product Area
Alerts