[Alert Rules] Bulk Editing Alert Rules without using the API is very slow
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 22h 21m
- Merged PRs (30d)
- 586
Description
### Problem Statement
I want to update the Slack channel used in all of my alerts but the UI makes this very challenging. Including but not limited to the project filters being applied to Alerts.
For example:
> Whatever project you've checked gets brought up to the top of the dropdown, which means that if I want to go through all of the projects in the list, I have to remember where in the list the project I'm looking at is and find it again to go to the "next" project in the list.
### Solution Brainstorm
Consider removing project filter limitations from the Alerts Overview - this would make it easier to iteratively alter alerts one at a time without needing to also iteratively page through projects.
Alternatively, provide a workflow that allows for the bulk editing of a specific field of a certain type of alerts. Most commonly this request is associated with updating the Slack channel used in multiple alerts (or similar Alert Rule Action).
Related to https://sentry.zendesk.com/agent/tickets/144631
### Product Area
Alerts
Contributor guide
Research direction
The issue points to the Alerts Overview and its project filters as the starting entry point; no files or tests are named. First clarify whether the accepted direction is removing those limitations or adding bulk editing for an alert field, then verify the chosen workflow supports updating Slack channels across the intended alerts.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100