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

# Issue Lifecycle

Follow the Issue journey from creation to completion with status transitions.

Issues progress through distinct stages from first detection to final resolution. Understanding this lifecycle helps teams systematically address errors while maintaining visibility into production health.

{% hint style="info" %}
**Systematic Error Resolution:** The Issue lifecycle provides a structured workflow from detection to resolution, ensuring every error pattern is tracked, prioritized, and addressed.
{% endhint %}

## The Complete Issue Journey

An Issue's lifecycle typically follows this path:

```mermaid
graph LR
    A[New] --> B[Triaged] --> C[Actioned] --> D[In Progress] --> E[In Review] --> F[Completed]
    F -.->|Regression detected| A
```

However, not all Issues follow every step. Some may be:

* Marked complete immediately (one-off errors)
* Duplicated under another Issue
* Removed if determined to be test data or irrelevant

## Status Field: The Lifecycle Tracker

The **Status** field drives Issue progression and filters the various list views used for operational workflows.

### Standard Status Values

Pharos ships with a set of standard status values that map to the stages above. Each one records what the Issue means, who sets it, and what should happen next.

**New**

* **Meaning:** Issue just created, never reviewed
* **Who sets it:** Pharos (automatically)
* **Next action:** Triage to assign priority
* **Typical duration:** Until next triage session (ideally <7 days)

**Triaged**

* **Meaning:** Issue reviewed, priority assigned
* **Who sets it:** Team member during triage
* **Next action:** Action high-priority Issues, monitor others
* **Typical duration:** Until actioned or re-evaluated

**Actioned**

* **Meaning:** Ticket created (Jira/Azure DevOps), assigned to someone
* **Who sets it:** Team member creating work item
* **Next action:** Developer begins investigation
* **Typical duration:** Until work begins

**In Progress**

* **Meaning:** Actively being worked on
* **Who sets it:** Developer investigating/fixing
* **Next action:** Implement and test fix
* **Typical duration:** Hours to weeks (depends on complexity)

**In Review**

* **Meaning:** Fix deployed, monitoring for recurrence
* **Who sets it:** Developer after deployment
* **Next action:** Wait for confirmation error stopped
* **Typical duration:** 1-2 weeks (monitoring period)

**Completed**

* **Meaning:** Fixed and verified, no longer occurring
* **Who sets it:** Developer or automatic (via ticketing integration)
* **Next action:** None (Issue archived from active views)
* **Typical duration:** Permanent (unless regression occurs)

**Duplicate**

* **Meaning:** Same problem as another Issue (marked duplicate)
* **Who sets it:** Team member or Pharos (automatic relating)
* **Next action:** Work on parent Issue instead
* **Typical duration:** Permanent

{% hint style="warning" %}
**Important:** The `New` and `Completed` statuses are special—they trigger specific Pharos behaviors (see Regression Detection below). Other statuses can be customized to match your workflow.
{% endhint %}

## Key Lifecycle Stages Explained

Each stage below describes what happens, which actions are automatic versus manual, and roughly how long it takes.

### 1. Creation

**What happens:**\
When a new error pattern is detected, Pharos creates an Issue record. The fingerprinting engine determines whether to create a new Issue or link the log to an existing one.

**Automatic actions:**

* Status set to `New`
* Priority set to `Medium` (default)
* Category, Functional Area inherited from first log
* First Occurred timestamp captured

**Duration:** Instantaneous (happens within seconds of error)

**Learn more:** [Creation](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/issue-lifecycle/creation.md)

***

### 2. Triaging

**What happens:**\
A team member reviews the Issue, examines impact metrics (users affected, data impacted, frequency), and assigns an appropriate priority based on business criticality.

**Manual actions:**

* Review occurrence patterns
* Check user and data impact
* Determine if business-critical process
* Assign priority (Lowest, Low, Medium, High, Highest)
* Set status to `Triaged`
* Add comment documenting reasoning

**Duration:** 1-5 minutes per Issue

**Learn more:** [Triaging](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/issue-lifecycle/triaging.md)

***

### 3. Actioning

**What happens:**\
High-priority Issues are escalated into the development workflow by creating work items (Jira tickets, Azure DevOps items) and assigning ownership.

**Manual actions:**

* Create ticket in bug tracker
* Link ticket URL to Issue's Bug Tracker field
* Set status to `Actioned`
* Add comment with ticket details

**Automated (with integration):**

* Ticket auto-created based on rules
* Issue status auto-updated
* Inline ticket view appears on Issue page

**Duration:** 1-2 minutes per Issue

**Learn more:** [Actioning](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/issue-lifecycle/actioning.md)

***

### 4. Resolution

**What happens:**\
A developer investigates the root cause, implements a fix, tests it, and deploys to production. The Issue is monitored to confirm the error stops occurring.

**Manual actions:**

* Use debug views, stack traces, and tracing
* Implement fix in sandbox
* Test thoroughly
* Deploy to production
* Update Issue status to `In Review` or `Completed`
* Add comment documenting fix

**Duration:** Hours to weeks (depends on complexity)

**Learn more:** [Resolution](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/issue-lifecycle/resolution.md)

***

### 5. Duplication Management

**What happens:**\
Related Issues representing the same underlying problem are linked together. Duplicate Issues are marked to avoid redundant work.

**Manual actions:**

* Identify related Issues (via Related Issues tab or manual inspection)
* Select Issues to mark duplicate
* System automatically sets oldest as parent
* Duplicates marked with `Duplicate` status

**Automatic:**\
Pharos relates Issues whose Logs share a Hash 2 or Hash 3 value (progressively looser hashes computed alongside the primary hash used to group logs into an Issue)

**Learn more:** [Duplication](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/issue-lifecycle/duplication.md)

***

### 6. Regression Detection

**What happens:**\
If a `Completed` Issue reoccurs (new log with same fingerprint arrives), Pharos automatically reopens it and flags it as regressed.

**Automatic actions:**

* Status reverts to `New`
* Regression checkbox set to `true`
* Regressed On date captured
* Resolved On cleared
* New ticket created (if ticketing integration enabled)

**Why this matters:**\
Catches incomplete fixes or newly introduced bugs, ensuring no solved problems are forgotten.

## Status Transitions: Allowed Paths

While you can manually set any status, typical progressions follow these patterns:

```mermaid
graph LR
    A[New] --> B[Triaged] --> C[Actioned] --> D[In Progress] --> E[In Review] --> F[Completed]
    B -.->|Low priority, no action needed| F
    B --> G[Duplicate - of another Issue]
    F -.->|Regression detected| A
```

{% hint style="info" %}
**Custom Statuses:** Your organization may add custom status values (e.g., "Pending Vendor," "Blocked," "Won't Fix"). Just ensure `New` and `Completed` remain as-is for Pharos automation to function correctly.
{% endhint %}

## Priority Field: Independent of Status

Priority is assigned **during triage** and can change **at any time** based on:

* Occurrence frequency increasing
* User impact growing
* Business process becoming critical
* External dependencies changing

### Priority Values

Pharos uses five priority values, each tied to impact criteria and a typical action:

| Priority    | Criteria                                                             | Typical Action                                 |
| ----------- | -------------------------------------------------------------------- | ---------------------------------------------- |
| **Highest** | User-facing, revenue-impacting, >50 users, no workaround             | Fix within 24 hours, create ticket immediately |
| **High**    | Daily occurrence, data integrity risk, >10 users, workaround painful | Fix within 1 week, create ticket               |
| **Medium**  | Persistent but low impact, <10 users, business operates normally     | Fix within 1 month or backlog                  |
| **Low**     | Sporadic, no user reports, minimal impact, edge case                 | Backlog only, re-evaluate monthly              |
| **Lowest**  | One-time occurrence, test data, non-production                       | Monitor only, may close proactively            |

Priority is **not** tied to status. An Issue can be:

* `New` with `Highest` priority (just discovered, very critical)
* `Triaged` with `Low` priority (reviewed, not urgent)
* `Actioned` with `Medium` priority (ticket created, moderate urgency)

## Measuring Issue Lifecycle Health

Track these metrics to understand your Issue resolution velocity:

| Metric                   | Calculation                                          | Target     | Insight                                |
| ------------------------ | ---------------------------------------------------- | ---------- | -------------------------------------- |
| **Time in New**          | Days from creation to first triage                   | <7 days    | Are we staying on top of new problems? |
| **Triage to Action**     | Days from `Triaged` to `Actioned` (for High/Highest) | <3 days    | Are critical issues escalated quickly? |
| **Action to Resolution** | Days from `Actioned` to `Completed`                  | <14 days   | How fast are we fixing bugs?           |
| **Regression Rate**      | % of Completed Issues that reopen                    | <5%        | Are our fixes effective?               |
| **Open Issue Trend**     | Week-over-week change in open count                  | Decreasing | Is backlog shrinking or growing?       |

## Example: Full Lifecycle Walkthrough

The timeline below traces a single Issue from detection through resolution and an eventual regression.

**Day 1 (Monday, 9:00 AM):** Flow breaks in production\
→ Log created → Issue auto-created (Status: `New`, Priority: `Medium`)

**Day 3 (Wednesday, 2:00 PM):** Weekly triage session\
→ Dustin reviews Issue → Sees 15 users impacted, daily occurrence, order processing affected\
→ Assigns `Highest` priority, sets status to `Triaged`, adds comment: "Order flow breaking daily, 15 users, revenue-impacting"

**Day 3 (Wednesday, 2:05 PM):** Action taken\
→ Dustin creates Azure DevOps work item, links URL, sets status to `Actioned`

**Day 4 (Thursday, 10:00 AM):** Developer picks up ticket\
→ Dan starts investigation, sets status to `In Progress`

**Day 4 (Thursday, 3:00 PM):** Root cause found\
→ Validation rule missing null check, fix deployed to sandbox, tested

**Day 5 (Friday, 11:00 AM):** Deployed to production\
→ Dan deploys fix, sets status to `In Review`, adds comment: "Added null check to validation rule, monitoring for recurrence"

**Day 12 (Next Friday):** No recurrence\
→ Dan confirms no new logs, sets status to `Completed`

**Day 45 (6 weeks later):** Regression!\
→ New log arrives with same fingerprint → Pharos reopens Issue (Status: `New`, Regression: `true`)\
→ Alert sent, team investigates → Discovers related flow also needs fix

***

## Explore Each Lifecycle Stage

<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>🆕 Creation</strong></td><td>When a new Issue is created vs. leveraging an existing issue through fingerprinting.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/issue-lifecycle/creation.md">Creation</a></td></tr><tr><td><strong>⚖️ Triaging</strong></td><td>The issue triage process, and how to implement periodic issue review effectively.</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>🎬 Actioning</strong></td><td>Actioning issues by placing them in a backlog or assigning to an engineer.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/issue-lifecycle/actioning.md">Actioning</a></td></tr><tr><td><strong>✅ Resolution</strong></td><td>How Pharos helps resolve problems through AI analysis and tracing.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/issue-lifecycle/resolution.md">Resolution</a></td></tr><tr><td><strong>🔀 Duplication</strong></td><td>When and why to mark issues as duplicates, and how it affects statistics.</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>🗑️ Removal</strong></td><td>The process of removing issues and the relationship with underlying logs.</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>
