diff --git a/docs/product/issues/issue-priority/index.mdx b/docs/product/issues/issue-priority/index.mdx index b90ccf73a04a7..a516e1c218d1c 100644 --- a/docs/product/issues/issue-priority/index.mdx +++ b/docs/product/issues/issue-priority/index.mdx @@ -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." --- @@ -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: