Skip to content

Commit cb81f21

Browse files
snigdhaslizokm
authored andcommitted
chore(issue-priority): Update documentation for enhanced issue priority (#10934)
* Update documentation for enhanced issue priority * Apply suggestions from code review * Apply suggestions from code review Co-authored-by: Liza Mock <liza.mock@sentry.io> --------- Co-authored-by: Liza Mock <liza.mock@sentry.io>
1 parent 9f733f2 commit cb81f21

File tree

1 file changed

+11
-1
lines changed

1 file changed

+11
-1
lines changed

docs/product/issues/issue-priority/index.mdx

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,14 +8,24 @@ Issue priority sorts the issues Sentry receives into **High**, **Medium** and **
88

99
## How Priority Works
1010

11-
When Sentry receives an event, it assigns a priority to the issue based on the event's **log level** (for error issues) or **actionability** (for non-error issues like performance). For Python and Javascript projects, Sentry will also consider the error message, whether or not the error is handled, and historical actions taken on similar issues.
11+
When Sentry receives an event, it assigns a priority to the issue based on the event's **log level** (for error issues) or **actionability** (for non-error issues like performance).
1212

1313
There are three discrete priority levels for issues in Sentry:
1414

1515
- **High**: Issues that are likely to be actionable and require immediate attention.
1616
- **Medium**: Issues that are likely to be actionable and require attention in the near future.
1717
- **Low**: Issues that don't require immediate attention.
1818

19+
### Enhanced Issue Priority
20+
21+
<Note>
22+
23+
This feature is available only if your organization is on either a [Business](https://sentry.io/pricing/) or [Trial](/pricing/#product-trials) Plan.
24+
25+
</Note>
26+
27+
In addition to the log level or actionability, the enhanced priority calculations will consider factors such as the error message, whether or not the error is handled, and historical actions taken on similar issues, when determining the priority of an issue for Python or JavaScript projects.
28+
1929
### Automatic Priority Updates
2030

2131
Sentry continuously monitors the volume of events for each issue. If there's a surge of events for a particular issue (it escalates), its priority level will be automatically bumped up. See the [escalating issues algorithm](/product/issues/states-triage/escalating-issues/) for more information on how escalations are identified. When an issue de-escalates, its priority will go back down to the previous level.

0 commit comments

Comments
 (0)