[Home](../../) › [Support](../../support.md) › [Support Policies](../policies.md) › Bug Prioritization

# Bug Prioritization

> Explains how we assign bug severities and when we resolve them.

Canonical: https://postsharp.net/support/policies/prioritization.html

## Bug Prioritization

We assign priorities to bug fixes based on the following rules:

| Severity  | Description                                                                 | Scheduling          |
|-----------|-----------------------------------------------------------------------------|---------------------|
| Cosmetic  | The product works as intended, but its UI or output contains typos or formatting issues. | Backlog            |
| Annoying  | A specific feature does not function as intended, but the use case has never worked before. | Backlog            |
| High      | The entire product is unusable, or there is a regression in an important feature, but downgrading is possible. | Next business day  |
| Critical  | A large number of developers are blocked, and there is no workaround, not even rolling back to a previous build. | Immediate attention |

_Backlog_ typically means that fixing these bugs will be considered when the team is not overloaded, typically when we are not focused on a feature-oriented release.

> **Note**
>
> Enterprise customers can escalate issues from Annoying to High, after discussion with the core team. To escalate a GitHub issue, please [open a private support ticket](https://postsharp.net/support).

---

## Site navigation

- Previous: [Service Levels](sla.md)
- Index of the whole site: [llms.txt](../../llms.txt)