--- title: "Issue Status" description: "Learn how issue status works and and how to triage issues." url: https://docs.sentry.io/product/issues/states-triage/ --- # Issue Status Use the status tags attached to issues on the [**Issues** page](https://sentry.io/issues/) in Sentry to help you triage and prioritize problems with your application that are important to you. Keep in mind that an issue can only have **one status at a time.** Here's a list of all statuses, how they're assigned to an issue, and their custom search term: | Status | Condition | Custom Search Term | | -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------ | | **New** | An issue that was created in the last 7 days. | is:new | | **Ongoing** | An issue that was created more than 7 days ago or has manually been marked as reviewed. | is:ongoing | | **Escalating** | An issue that's exceeded its forecasted event volume. For more details, see [Escalating Issues Algorithm](https://docs.sentry.io/product/issues/states-triage/escalating-issues.md). Please note that escalating issues currently does not work for merged/unmerged issues. | is:escalating | | **Regressed** | A resolved issue that's come up again. | is:regressed | | **Archived** | An issue that's been marked as archived. | is:archived | | **Resolved** | An issue that's been marked as fixed. | is:resolved | The diagram below shows how the statuses are updated automatically and manually: By default, the list on the **Issues** page is narrowed down to unresolved issues, with `New`, `Ongoing`, `Escalating`, and `Regressed` status. You can update the filter by changing the attributes in the search bar at the top of the page. ## [Manually Triaging Issues](https://docs.sentry.io/product/issues/states-triage.md#manually-triaging-issues) While some issue statuses are added and updated automatically, you can manually `Archive` or `Resolve` an issue, which will also change its status and mark it as reviewed. Items filtered under `is:for_review` are new, regressed, or unresolved issues that haven't been marked as reviewed yet. ### [Archive](https://docs.sentry.io/product/issues/states-triage.md#archive) Archive an issue to move it out of the issue stream and pause alerts on it until the issue gets worse. Archiving makes sense for noisy issues that are less pressing or not applicable to you or your team. Archiving changes the issue status to `Archived`. Sentry will automatically bring an issue back to the top of the list and change its status to `Escalating` if the events in that issue significantly increase over a short period of time. To learn more about how this works, see [Escalating Issues Algorithm](https://docs.sentry.io/product/issues/states-triage/escalating-issues.md). By default, issues are archived until escalating. There's also an option to mark an issue as `Archived` for: * Forever * A set period of time * Until it occurs a set number of times * Until a set number of users are affected If you archive an issue "Forever", events connected with that issue will continue to be recorded, but the issue will never be labeled as escalating even if it meets escalating conditions. You can still unarchive any archived issue, including those that have been archived "Forever". ### [Resolve](https://docs.sentry.io/product/issues/states-triage.md#resolve) You can manually mark an issue as `Resolved` when it’s been fixed. A plain **Resolve** treats any later event as a regression. If you use [releases](https://docs.sentry.io/product/releases.md), you can resolve an issue in a specific release instead. That tells Sentry which versions still count as expected noise and which newer versions should count as a regression. For more detail on how release comparison works, see [3 Different Ways to Resolve Issues](https://docs.sentry.io/product/releases.md#3-different-ways-to-resolve-issues). * **The next release**: Resolve once the next release ships. Use when the fix is ready but not deployed yet. * Example: Fix is in `main`, prod is still on `1.8.0` β€” only a recurrence in `1.9.0+` reopens it. * **The current release**: Resolve in the project's current/latest release. Use when the fix is already live. * Example: Fix shipped in `2.4.1` β€” leftover `2.4.0` events stay quiet; `2.4.2+` can regress it. * **Another existing release**: Resolve in a release you choose. Use for hotfixes or versions that aren't current. * Example: Hotfix went out in `3.1.4` while latest is `3.2.0` β€” anchor resolution to `3.1.4`. You can also resolve by [including the issue ID in a commit or pull request associated with a release](https://docs.sentry.io/product/releases/associate-commits.md#resolve-issues-by-commit). If the same issue comes back in a newer release than the one you resolved it in, its status will automatically change to `Regressed`. ### [Delete](https://docs.sentry.io/product/issues/states-triage.md#delete) You can remove an issue from the issue list by deleting it, but it will reappear as a new issue if it recurs. There's also an option to `Delete and Discard Forever`, which will make it so that the issue is never seen again, even if it recurs. Any future events tied to the permanently deleted issue will be discarded automatically and won't count towards [your quota](https://docs.sentry.io/pricing/quotas.md). Discard forever only works for [Error Issues](https://docs.sentry.io/product/issues/issue-details/error-issues.md?original_referrer=https%3A%2F%2Fdocs.sentry.io%2Fproduct%2Fissues%2Fstates-triage%2F). Other issue categories, such as [Performance Issues](https://docs.sentry.io/product/issues/issue-details/performance-issues.md?original_referrer=https%3A%2F%2Fdocs.sentry.io%2Fproduct%2Fissues%2Fstates-triage%2F) only support normal deletion. ## Pages in this section - [Escalating Issues Algorithm](https://docs.sentry.io/product/issues/states-triage/escalating-issues.md)