0
Let direct-member issue alerts bypass personal alert filter
Source: getsentry/sentry#129185 · opened by @sentry-junior[bot]
Users want to turn off issue alerts they receive *implicitly* (for example as a recently active member through fallthrough, or as a suggested assignee/issue owner) while still receiving issue alerts whose action explicitly notifies them as a member. Today the single "Issue Alert Notifications" setting covers both cases. Raised by Zsofia Papp after a user with the setting Off did not receive a test email from an alert configured to notify them directly. Current behavior • For a "Notify Member" action, get_send_to() resolves the user in determine_eligible_recipients() and then filters them through _get_recipients_by_provider() using the user's ISSUE_ALERTS setting, the same filter applied to issue owners, suggested assignees, suspect committers, and fallthrough recipients (src/sentry/notifications/utils/participants.py). • GetSendToMemberTest.test_send_to_user in tests/sentry/notifications/utils/test_participants.py asserts that a direct member with…
No pledges yet. Be the first to back this.
Comments
Similar requests
Support webhooks for spike protection alerts so partners can build alerts for these too
15 votes · 0 comments
Alerts - Be able to get alerts based on Frozen/Slow frame rates
0 votes · 0 comments
Alerts - I want to be able to get alerts based on the differences between releases
0 votes · 0 comments
Alerts - Getting alerts on status change Ongoing -> Escalating
2 votes · 0 comments
Use the original baseline for % based alerts
0 votes · 0 comments
No comments yet.