> For the complete documentation index, see [llms.txt](https://docs.pharos.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/issue-lifecycle/removal.md).

# Removal

Understand the process of removing issues and the relationship with underlying logs.

Sometimes an Issue does not warrant tracking—test data, known non-issues, or one-off environmental glitches. Removal is the process of cleaning up these Issues from your active backlog while preserving the relationship with underlying logs.

***

## When to Remove an Issue

Remove an Issue when it does not represent a real problem worth tracking. The common scenarios are:

| Scenario            | Action                                                                                                                                                                                                 |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Test data**       | Errors from test users, sandbox refreshes, or automated test runs                                                                                                                                      |
| **Known non-issue** | Expected behavior (e.g., "User cancelled" or intentional validation)                                                                                                                                   |
| **One-off**         | Environmental glitch, transient network issue, or external system outage                                                                                                                               |
| **Won't fix**       | Low impact, no business case to fix, or deprecated feature                                                                                                                                             |
| **Duplicate**       | Mark as [Duplicate](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/issue-lifecycle/duplication.md) instead of removal when it's the same problem as another Issue |

***

## Removal vs. Completion

Removal and completion both take an Issue out of your active backlog, but they mean different things:

| Action        | Meaning                                                          |
| ------------- | ---------------------------------------------------------------- |
| **Completed** | Issue was fixed; error no longer occurs                          |
| **Removed**   | Issue is not a real problem; no fix needed, exclude from backlog |

Use **Completed** when you resolved the root cause. Use **Removal** (or equivalent status) when the Issue should not be part of your triage workflow.

***

## Relationship with Logs

When an Issue is removed:

* **Logs remain** — The underlying log records are typically not deleted; they retain the lookup to the Issue
* **Issue visibility** — Removed Issues are excluded from active list views (New, Open, High Priority)
* **Audit trail** — Historical record is preserved for reporting and audit

Different configurations may support hard delete vs. soft delete (status change). Check your org's settings.

***

## Impact on Metrics

Removed Issues are excluded from:

* Open Issue count
* Triage backlog
* Resolution velocity (they were never "resolved")
* Regression tracking (removed Issues don't reopen)

***

## Best Practices

A few habits keep removals clean and auditable:

* **Document reason** — Add a comment before removing (e.g., "Test user; not production")
* **Review periodically** — If the same "removed" pattern keeps reappearing, reconsider
* **Use filters** — Create a "Removed" or "Won't Fix" view to audit removals

***

## Related

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>♻️ Issue Lifecycle</strong></td><td>Full lifecycle overview</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/issue-lifecycle.md">Issue Lifecycle</a></td></tr><tr><td><strong>🔀 Duplication</strong></td><td>Marking related Issues</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/issue-lifecycle/duplication.md">Duplication</a></td></tr><tr><td><strong>⚖️ Triaging</strong></td><td>Prioritization decisions</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/issue-lifecycle/triaging.md">Triaging</a></td></tr></tbody></table>
