-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Issue archiving beta #6980
Issue archiving beta #6980
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
You must have Developer access to commit code to Sentry on Vercel. If you contact an administrator and receive Developer access, commit again to see your changes. Learn more: https://vercel.com/docs/concepts/teams/roles-and-permissions#enterprise-team-account-roles |
|
||
Sentry defines an issue as `Escalating` when the number of events is significantly higher than the previous week. | ||
|
||
The escalating issues algorithm uses historical data from the previous week to calculate thresholds for the next week on a per-issue basis. If an issue exceeds its predetermined threshold, it gets tagged as "escalating." An escalating issue is automatically surfaced in the "Unresolved" and "Escalating" tabs, even if the issue was previously archived. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we clarify that this only applies to issues that are marked as archived until escalating
? The last bit leaves it open-ended.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated the wording. I thought any archived issue can be escalated unless it was "archived forever". LMK if this isn't correct.
src/docs/product/issues/states-triage/escalating-issues/index.mdx
Outdated
Show resolved
Hide resolved
|
||
Sentry defines an issue as `Escalating` when the number of events is significantly higher than the previous week. | ||
|
||
The escalating issues algorithm uses historical data from the previous week to calculate thresholds for the next week on a per-issue basis. If an issue exceeds its predetermined threshold, it gets tagged as "escalating." An escalating issue is automatically surfaced in the "Unresolved" and "Escalating" tabs, even if the issue was previously archived. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated the wording. I thought any archived issue can be escalated unless it was "archived forever". LMK if this isn't correct.
src/docs/product/issues/states-triage/escalating-issues/index.mdx
Outdated
Show resolved
Hide resolved
src/docs/product/issues/states-triage/escalating-issues/index.mdx
Outdated
Show resolved
Hide resolved
add redirect to right page
This will be a beta page for the 100 orgs beta testing archiving issues. PLEASE DO NOT MERGE INTO MASTER.