|
| 1 | +--- |
| 2 | +title: "Issue Archiving" |
| 3 | +sidebar_order: 1 |
| 4 | +description: "Learn how issue status works and and how to triage issues." |
| 5 | +--- |
| 6 | + |
| 7 | +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.** |
| 8 | + |
| 9 | +Here's a list of all statuses, how they're assigned to an issue, and their custom search term: |
| 10 | + |
| 11 | +| Status | Condition | Custom Search Term | |
| 12 | +| -------------- | --------------------------------------------------------------------------------------- | ------------------ | |
| 13 | +| **New** | An issue that was created in the last 7 days. | is:new | |
| 14 | +| **Ongoing** | An issue that was created more than 7 days ago or has manually been marked as reviewed. | is:ongoing | |
| 15 | +| **Escalating** | An issue that's exceeded its forecasted event volume. | is:escalating | |
| 16 | +| **Regressed** | A resolved issue that's come up again. | is:regressed | |
| 17 | +| **Archived** | An issue that's been marked as archived. | is:archived | |
| 18 | +| **Resolved** | An issue that's been marked as fixed. | is:resolved | |
| 19 | + |
| 20 | +The diagram below shows how the statuses are updated automatically and manually: |
| 21 | + |
| 22 | + |
| 23 | + |
| 24 | +One way to limit the issues that you see is by selecting a tab at the top of the **Issues** page. On the “Unresolved" tab, you'll find `New`, `Ongoing`, `Escalating`, and `Regressed` issues. You can also narrow down further by choosing the "For Review", "Regressed", "Escalating", or "Archived" tabs. |
| 25 | + |
| 26 | +## Manually Triaging Issues |
| 27 | + |
| 28 | +While some issue statuses are added and updated automatically, you can manually `Archive` or `Resolve` an issue, which will also change its status. |
| 29 | + |
| 30 | +### Archive |
| 31 | + |
| 32 | +You can manually archive issues that are less pressing or not applicable to you or your team. This will change their status to `Archived` and remove them from the issues list. 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. There's also an option to mark an issue as `Archived` for: |
| 33 | + |
| 34 | +- A set period of time |
| 35 | +- Until it occurs a set number of times |
| 36 | +- Until a set number of users are affected |
| 37 | + |
| 38 | +### Resolve |
| 39 | + |
| 40 | +You can manually mark an issue as `Resolved` when it’s been fixed. You can also specify further by resolving it in: |
| 41 | + |
| 42 | +- Your next release |
| 43 | +- A current release |
| 44 | +- Another release |
| 45 | + |
| 46 | +or |
| 47 | + |
| 48 | +- By [including the issue ID in a commit](/product/releases/associate-commits#resolve-issues-by-commit) |
| 49 | + |
| 50 | +If the same issue comes back, its status will automatically change to `Regressed`. |
| 51 | + |
| 52 | +### Delete |
| 53 | + |
| 54 | +You can remove an issue from the issue list by deleting it, but it will reappear as a new issue if it recurs. |
| 55 | + |
| 56 | +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](/product/accounts/quotas/). |
| 57 | + |
| 58 | +<Note> |
| 59 | + |
| 60 | +You can only delete [Error Issues](/product/issues/issue-details/error-issues/). Other issue categories, (such as [Performance Issues](/product/issues/issue-details/performance-issues/)), don't support this feature. |
| 61 | + |
| 62 | +</Note> |
![getsantry[bot]](https://avatars.githubusercontent.com/in/66573?v=4&size=40){kind=avatar}
0 commit comments