fix(alerts): Consider all ESCALATING substatus transitions as 'has_escalated' in alerts#108084
Merged
fix(alerts): Consider all ESCALATING substatus transitions as 'has_escalated' in alerts#108084
Conversation
Member
Author
|
TODO: Doc change? |
github-actions
bot
added
the
Scope: Backend
Member
Author
wedamija
approved these changes
Feb 11, 2026
…calated' in alerts
Member
Author
|
@sfanahata If you could point me to any doc updates that this might require, I'm happy to follow up with that. I didn't see anything obvious. |
jaydgoss
pushed a commit
that referenced
this pull request
Feb 12, 2026
…calated' in alerts (#108084) Previously, 'snooze until count' didn't result in has_escalated being set, which meant that our escalation-focused conditions didn't trigger. This plugs that hole and documents the meaning a bit more clearly. Fixes ISWF-608.
Contributor
|
@kcons @sfanahata I think the docs for this are already in a good spot... for example: https://docs.sentry.io/product/issues/states-triage/escalating-issues/ And the current docs on issue alerts seem to align with this behaviour as well: https://docs.sentry.io/product/alerts/create-alerts/issue-alert-config/#when-conditions-triggers |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Previously, 'snooze until count' didn't result in has_escalated being set, which meant that our escalation-focused conditions didn't trigger.
This plugs that hole and documents the meaning a bit more clearly.
Fixes ISWF-608.