Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feat(Escalation policies): A Hackweek project #76386

Draft
wants to merge 39 commits into
base: master
Choose a base branch
from

Conversation

mikejihbe
Copy link
Contributor

Adds escalation policies, escalation policy state management, rotation schedules, alerts that trigger escalation policies, associated views for all of the above.

@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Aug 19, 2024
@mikejihbe mikejihbe changed the title Feat: Escalation policies (Hackweek) Feat(Escalation policies): A Hackweek project Aug 19, 2024
mikejihbe and others added 2 commits August 20, 2024 09:53
…alation policy endpoints (#76393)

Adds FE hooks for the following endpoints: 

* GET `organization/<org>/escalation-policies/`
* PUT `organization/<org>/escalation-policies/`
* GET `organization/<org>/escalation-policies/<policy_id>`
* DELETE `organization/<org>/escalation-policies/<policy_id>`
* GET `organization/<org>/rotation-schedules/`
* PUT `organization/<org>/rotation-schedules/`
* GET `organization/<org>/rotation-schedules/<policy_id>`
* DELETE `organization/<org>/rotation-schedules/<policy_id>`
@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Aug 20, 2024
Adds Routes for the Schedule and Escalation Policies pages within the
Alerts product section
Copy link
Contributor

🚨 Warning: This pull request contains Frontend and Backend changes!

It's discouraged to make changes to Sentry's Frontend and Backend in a single pull request. The Frontend and Backend are not atomically deployed. If the changes are interdependent of each other, they must be separated into two pull requests and be made forward or backwards compatible, such that the Backend or Frontend can be safely deployed independently.

Have questions? Please ask in the #discuss-dev-infra channel.

MichaelSun48 and others added 2 commits August 21, 2024 15:26
…ble (#76472)

* Made status a badge instead of text
* Switched status and title ordering 
* "Fixed" the table grid spacing 
* Added loading state 
* Added some gap between the escalation policy cards 
* Fixed caching bug for the PUT escalation-policy-states endpoint 


![image](https://github.com/user-attachments/assets/c5138aff-387c-43ba-b212-136a5c461590)
@getsantry
Copy link
Contributor

getsantry bot commented Sep 13, 2024

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you remove the label Waiting for: Community, I will leave it alone ... forever!


"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

@getsantry getsantry bot added Stale and removed Stale labels Sep 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Scope: Backend Automatically applied to PRs that change backend components Scope: Frontend Automatically applied to PRs that change frontend components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants