> 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/duplication.md).

# Duplication

Learn when and why to mark issues as duplicates and how it affects statistics.

Duplicate Issues represent the same underlying problem—caught by different fingerprints or created before fingerprinting consolidated them. Marking Issues as duplicates keeps your backlog clean and prevents redundant work while preserving the relationship for context.

***

## When to Mark Duplicates

| Scenario                 | Action                                                                                                   |
| ------------------------ | -------------------------------------------------------------------------------------------------------- |
| **Same root cause**      | Two Issues describe the same bug (e.g., null pointer in same method, different stack traces)             |
| **Related errors**       | One Issue is a symptom of another (e.g., flow failure caused by validation rule)                         |
| **Fingerprint variance** | Pharos created separate Issues for what is logically one problem (e.g., different record IDs in message) |
| **Consolidation**        | Multiple Issues were created before fingerprinting improved; now they should be merged                   |

***

## How Duplication Works

When you mark an Issue as duplicate:

1. **Parent selection** — Pharos designates the older Issue as the parent (or you choose)
2. **Status** — The duplicate Issue is set to `Duplicate`
3. **Relationship** — A lookup or related record links the duplicate to the parent
4. **Workflow** — Team focuses on the parent; duplicate is excluded from active triage views

***

## Impact on Statistics

| Consideration   | Behavior                                                                                                 |
| --------------- | -------------------------------------------------------------------------------------------------------- |
| **Log count**   | Duplicate's logs may remain linked to the duplicate Issue or roll up to parent—depends on implementation |
| **User impact** | Parent Issue's impact metrics may or may not include duplicate's users; verify rollup behavior           |
| **List views**  | Duplicate Issues are typically filtered out of "Open" and "New" views                                    |
| **Reporting**   | Reports can filter by `Status != Duplicate` to avoid double-counting                                     |

***

## Automatic Related Issues

Pharos may automatically relate Issues whose Logs share a **Hash 2 or Hash 3** value — progressively looser hashes computed alongside the primary `pharos__Hash_1__c` used to group logs into an Issue. A match sets the newer Issue's `pharos__Related_Issue__c` lookup to point at the matching Issue, and it appears in the **Related Issues** list. You can then manually mark one as a duplicate of the other if they represent the same problem.

***

## Best Practices

* **Mark early** — When you identify a duplicate during triage, mark it immediately to avoid redundant investigation
* **Document reason** — Add a comment explaining why it's a duplicate (e.g., "Same as ISS-00042, different user context")
* **Verify parent** — Ensure the parent Issue is the one you want to track; resolution of the parent should resolve the duplicate

***

## 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>⚖️ Triaging</strong></td><td>Prioritization and assignment</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/issue-lifecycle/triaging.md">Triaging</a></td></tr><tr><td><strong>🗑️ Removal</strong></td><td>Cleaning up non-issues</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/issue-lifecycle/removal.md">Removal</a></td></tr></tbody></table>
