> 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/how-pharos-does-it/action-and-collaboration.md).

# Action and Collaboration

Learn how Pharos facilitates triaging and collaborative resolution through  issue tracker and bugtracker integrations.

Awareness creates notifications, but notifications don't fix problems. The Action & Collaboration stage transforms alerts into systematic resolution through triage, prioritization, and integration with development workflows.

***

## The Challenge: From Alert to Resolution

Many organizations struggle with the gap between detecting errors and actually fixing them.

{% hint style="warning" %}
**Where Things Break Down:**

* Alerts go to Slack, get acknowledged, then forgotten
* No systematic process for deciding what to fix first
* Developers waste time gathering context that should have been captured
* Fixes happen in Jira, but Pharos issues aren't updated
* No way to track whether issues are actually getting resolved

**The result:** Technical debt accumulates, critical issues get deprioritized, and the team grows frustrated.
{% endhint %}

***

## The Pharos Solution: Systematic Issue Management

### Triaging: Data-Driven Prioritization

Issues arrive with aggregate metrics that enable informed decisions **without deep technical knowledge**. The numbers tell the story — no code reading required.

**Impact-based triage considers:**

* **User impact** — how many users are affected?
* **Data impact** — which objects and records are involved?
* **Occurrence pattern** — how frequently is this happening?
* **Functional area** — what part of the business does this touch?

{% hint style="info" %}
**Example Triage Decision (Admin Perspective):**

```mermaid
graph TD
    A[Issue: Apex Exception in OrderHandler]
    A --> M[Metrics Review]
    M --> M1[47 users affected - significant]
    M --> M2[823 Opportunities - revenue object]
    M --> M3[Daily occurrence for 2 weeks - persistent]
    M --> M4[Sales functional area - high priority]
    A --> D[Decision: HIGH PRIORITY]
    D --> A1[Action: Create Jira ticket for developer]
    D --> A2[Rationale: Large user impact on revenue-critical object]
```

No code knowledge required — the metrics tell the story.
{% endhint %}

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

***

### Collaboration: Issue Tracker

Issues serve as the central hub for collaboration, both inside Salesforce and in external development tools.

{% tabs %}
{% tab title="📋 In-Platform (Salesforce)" %}

* **Chatter integration** — team discussions directly on Issue records
* **Comments and notes** — capture investigation findings and decisions
* **Assignment** — route to specific users or queues
* **Status tracking** — follow the lifecycle from New → Triaged → Actioned → Completed
  {% endtab %}

{% tab title="🔧 External (Development Tools)" %}

* **Jira bidirectional sync** — status, comments, and context flow both ways
* **Azure DevOps integration** — link Issues to work items in your DevOps pipeline
* **Comment synchronization** — updates in one system appear in the other
  {% endtab %}
  {% endtabs %}

→ [Learn more about the Issue Tracker](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker.md)

***

### Bugtracker Integration: Closing the Loop

Pharos connects directly with your development workflow so that Issue context follows the problem all the way to resolution.

{% tabs %}
{% tab title="🖱️ Manual Ticket Creation" %}

* Review the Issue in Pharos
* Click "Create Ticket" to push it to Jira with full context
* A persistent link is maintained between the Issue and the ticket
  {% endtab %}

{% tab title="⚡ Automated Ticket Creation" %}

* Rules trigger ticket creation based on criteria you define
* **Critical errors** → immediate ticket + PagerDuty alert
* **High user impact** → ticket routed to the appropriate team queue
* **Reopened issues** → new ticket linked to the original
  {% endtab %}

{% tab title="🔄 Bidirectional Sync" %}

* Jira status changes → Pharos Issue status updates automatically
* Jira comments → appear in the Pharos timeline
* Issue reopens → a new Jira ticket is created and linked
  {% endtab %}
  {% endtabs %}

→ [Learn more about Jira Integration](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/ticketing-and-bugtracking.md)

***

## Collaboration Patterns

Teams adopt different workflows depending on their size, velocity, and risk tolerance. Here are three proven patterns:

{% tabs %}
{% tab title="📅 Weekly Triage Rotation" %}
**Setup:**

* Assign rotating triage responsibility across the team
* Hold weekly 30–60 minute triage sessions
* Review open Issues, assign priorities, and create tickets for High/Critical items

**Benefit:** Distributes knowledge across the team and prevents bottlenecks.
{% endtab %}

{% tab title="🚨 Automated Escalation" %}
**Setup:**

* Rules auto-create tickets for critical errors immediately
* Alert on-call team via PagerDuty with full Pharos context
* Link the alert directly to the Pharos Issue for investigation

**Benefit:** Zero-latency response for production emergencies.
{% endtab %}

{% tab title="🏃 Sprint Integration" %}
**Setup:**

* Triaged Issues are linked to the sprint backlog
* Team reviews the Pharos dashboard during sprint planning
* Track velocity by measuring Issues resolved per sprint

**Benefit:** Data-driven approach to reducing technical debt alongside feature work.
{% endtab %}
{% endtabs %}

***

## Measuring Success

Track these metrics to ensure your action and collaboration process is effective and improving over time:

| Metric                   | Target                | What It Means                                         |
| ------------------------ | --------------------- | ----------------------------------------------------- |
| **Triage Latency**       | <7 days               | Time from Issue creation to triage decision           |
| **Ticket Creation Rate** | >80% of High/Critical | How many high-priority Issues get formal tickets      |
| **Resolution Rate**      | Improving monthly     | Issues closed vs. created — is the backlog shrinking? |
| **Average Age**          | Decreasing            | How long Issues sit unresolved before someone acts    |

***

## From Action to Resolution

With systematic triage and integrated collaboration, teams can focus on actually fixing problems. The final stage — **Resolution** — provides the AI-powered tools and debugging capabilities needed to identify root causes and deploy fixes efficiently.

{% hint style="success" %}
**Next Step:** Learn how [Resolution](https://docs.pharos.ai/platform-overview/how-pharos-does-it/resolution.md) provides AI-powered analysis and debugging tools to fix issues faster.
{% endhint %}
