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

# Actioning

Learn about actioning issues by placing them in a backlog or assigning to an engineer.

After triaging issues and assigning priorities, the next step is taking action. Issues serve as backlog items that track problems requiring fixes or investigation.

## Issues as Backlog Items

The issue record functions like a ticket in a bug tracking system (Jira, Azure DevOps, etc.). It provides a centralized place where you can:

* Track the status of a known problem
* See the latest updates and occurrences
* Monitor impact metrics over time
* Document investigation findings and decisions
* Link to external tickets or work items

## Regular Backlog Review

**Review Cadence:**

You must look at your issue backlog regularly to prevent it from becoming overwhelming:

* **Weekly basis:** Recommended for most teams
* **Bi-weekly:** Acceptable for lower-volume environments
* **Monthly:** Maximum recommended interval

{% hint style="warning" %}
**Avoid Backlog Buildup**

If you don't review regularly, you'll end up with a larger and larger backlog, making it that much more daunting to address. Incremental review over time requires consistent effort but prevents being overwhelmed by sheer volume.
{% endhint %}

## Taking Action After Triage

Once an issue has been triaged and assigned a priority, take appropriate action:

### Creating Tickets

You can route an issue into a work item using either an external bug tracker or an internal Salesforce object, depending on how your team operates.

**External Bug Trackers (Jira, Azure DevOps):**

Pharos provides direct integration with external ticketing systems. You can create tickets from the issue record using the "Create Ticket" button, which:

* Pulls issue details into the ticket automatically
* Maintains a link between the Pharos issue and the external ticket
* Can use templates to standardize ticket creation

**Internal Salesforce Objects (Cases, Custom Request Objects):**

If you're not using external bug trackers, you can customize the issue Lightning page to add a "Create Request" button instead of "Create Ticket". This allows you to:

* Create internal work items (Cases, custom Request objects, etc.)
* Keep all tracking within Salesforce
* Integrate with your existing internal workflow

### Setting Status to "Triaged"

After reviewing an issue and making a priority decision, set the status to "Triaged". This signals to yourself and others that:

* The issue has been reviewed and analyzed
* Priority has been assigned
* Comments may have been left explaining the decision
* The issue is ready for the next step in the workflow

### Documenting Decisions

Always leave comments on the issue record when taking action:

```mermaid
graph TD
    A[TRIAGE OUTCOME]
    A --> B[Priority: High]
    A --> C[Action: Created Jira ticket PROJ-1234]
    A --> D[Assigned to: Development Team]
    A --> E[Notes: Impacts 23 users, daily occurrence, revenue-related]
```

This documentation is important:

* **For yourself:** When you review the issue again later
* **For team members:** Who may be looking at the issue for the first time
* **For continuity:** If someone else takes over the triage rotation

## Customizing the Issue Lightning Page

The issue record page is a Lightning page, giving you full flexibility to customize it for your workflow:

* Clone the Lightning page
* Remove the "Create Ticket" button if you don't use external bug trackers
* Add a "Create Request" button for internal ticketing
* Rearrange components to prioritize what's most important
* Add the Chatter feed component for easy commenting

{% hint style="info" %}
**Pro Tip: Adding Chatter for Comments**

To enable easy commenting on issues:

1. Edit the issue Lightning page
2. Add the Chatter Feed component (drag it to your preferred location)
3. This provides a convenient space for documenting triage decisions and action items
   {% endhint %}

## Priority-Based Action Guidelines

Refer back to the priorities assigned during triage to determine appropriate actions:

| Priority    | Action                                                                       |
| ----------- | ---------------------------------------------------------------------------- |
| **Highest** | Create ticket immediately, notify on-call team, assign to specific developer |
| **High**    | Create ticket, add to sprint backlog, include in weekly planning             |
| **Medium**  | Create ticket OR add to backlog, document findings, re-evaluate monthly      |
| **Low**     | Do NOT create ticket, add detailed notes explaining why, set review date     |
| **Lowest**  | Monitor only; close proactively if no business impact                        |

## Next Steps

After actioning an issue:

* The issue remains open and continues to aggregate new occurrences
* Track progress through the issue status field
* Update the issue as work progresses (In Progress, In Review, etc.)
* When the underlying problem is fixed, mark the issue as Completed
* If the issue reoccurs after being marked Completed, Pharos will automatically reopen it
