Alert - "Send Test Notification" fails when the triggering user isn't a member of the projects attached to the alert
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 23m
- Merged PRs (30d)
- 607
Description
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
- Create a Alert in an org and attach monitors from projects the current user is not a member of (via team membership).
- Click "Send Test Notification."
- The test fails with the error "No projects found for this organization that the user has access to"
Expected Result
Alerts are designed as standalone notification configurations that can be attached to any monitor in the org the user's team membership in specific projects shouldn't gate whether a test notification can be sent. The alert config itself has the project context; the user's membership is irrelevant to notification delivery.
Actual Result
No projects found for this organization that the user has access to
Product Area
Alerts
Link
No response
DSN
No response
Version
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Send Test Notification request path and the project-access lookup described by the error. Trace how attached monitor projects are selected, then verify that a user who is not a member of those projects can still send a test notification for the alert.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100