feat(issue-priority): Add new page for issue priority (#9452)

Author: malwilley

Diff for: docs/product/issues/issue-priority/index.mdx

@@ -0,0 +1,45 @@
+---
+title: Issue Priority
+sidebar_order: 31
+description: "Learn how Sentry determines the level of issue severity and prioritizes issue importance accordingly."
+---
+
+<Note>
+
+This feature is only available to Early Adopters. To opt in, make sure your organization's [Early Adopter toggle](https://sentry.io/orgredirect/organizations/:orgslug/settings/organization/) is on.
+
+Have feedback? Please let us know in the [GitHub discussion](https://github.com/getsentry/sentry/discussions/68908).
+
+</Note>
+
+Issue priority sorts the issues Sentry receives into **High**, **Medium** and **Low** priority buckets. This helps you identify and address critical, high-priority errors that may be impacting your application's functionality and user experience first.
+
+## 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.
+
+There are three discrete priority levels for issues in Sentry:
+
+- **High**: Issues that are likely to be actionable and require immediate attention.
+- **Medium**: Issues that are likely to be actionable and require attention in the near future.
+- **Low**: Issues that don't require immediate attention.
+
+### Automatic Priority Updates
+
+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.
+
+### Manual Priority Updates
+
+You can update issue priority manually at any time, either from the issue details page or from the issue stream. But once an issue's priority has been changed manually, it will no longer be automatically adjusted if the event volume escalates.
+
+## Priority in the Issue Stream
+
+By default, the issue stream on the **Issues** page filters out low-priority issues. If you'd like to be able to see low-priority issues, you can [set your default search](/product/reference/search/saved-searches/#set-a-default-search) to include them.
+
+When viewing the "Prioritized" tab, you can quickly triage issues by using the priority dropdown. Low-priority issues will disappear from the "Prioritized" tab once their priority is updated.
+
+![Issue Priority Dropdown](/product/issues/issue-priority/issue-priority-dropdown.png)
+
+You may also update the priority level of multiple issues at once by selecting them and using the bulk action dropdown.
+
+![Issue Priority Bulk Update](/product/issues/issue-priority/issue-priority-bulk-edit.png)

Diff for: docs/product/issues/suspect-commits/index.mdx

@@ -1,6 +1,6 @@
 ---
 title: Suspect Commits
-sidebar_order: 31
+sidebar_order: 32
 description: "Learn how integrations enable suspect commits."
 ---