Skip to content

Commit

Permalink
fix(issues): severity -> actionability (#10227)
Browse files Browse the repository at this point in the history
  • Loading branch information
mrduncan committed May 31, 2024
1 parent efd8030 commit 9d356ae
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/product/issues/issue-priority/index.mdx
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
title: Issue Priority
sidebar_order: 31
description: "Learn how Sentry determines the level of issue severity and prioritizes issue importance accordingly."
description: "Learn how Sentry prioritizes issue actionability."
---

<Note>
Expand All @@ -16,7 +16,7 @@ Issue priority sorts the issues Sentry receives into **High**, **Medium** and **

## How Priority Works

When Sentry receives an event, it assigns a priority to the issue based on the event's **log level** (for error issues) or **severity** (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.
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.

There are three discrete priority levels for issues in Sentry:

Expand Down

0 comments on commit 9d356ae

Please sign in to comment.