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

# Accessing Issues

Learn how to find and access issues in Salesforce using standard tools.

Pharos provides multiple pathways to access and navigate Issues, designed to support different workflows and use cases. Whether you're triaging a backlog, investigating a specific error, or analyzing trends, there's a view optimized for your needs.

## Primary Access Methods

There are four primary ways to reach Issues—list views, log-to-Issue navigation, search, and reports and dashboards—each suited to a different workflow.

### 1. List Views

List views are the most common way to browse and filter Issues.

**Standard Views:**

* **All Open Issues:** Everything not marked as Completed
* **New Issues:** Recently created, not yet triaged
* **High Priority:** Highest and High priority Issues requiring immediate attention
* **My Issues:** Assigned to you
* **Recently Viewed:** Your last accessed Issues

**Custom Views:**\
You can create filtered views based on any Issue field:

* Issues from a specific Functional Area (Apex, Flow, Process Builder)
* Issues affecting specific Objects (Account, Opportunity, Case)
* Issues older than 30 days (aging backlog)
* Issues with regressions (previously resolved, now back)

**Typical Columns in List Views:**

* **Issue Name:** Auto-generated from error type
* **Status:** Current lifecycle stage
* **Priority:** Assigned importance
* **Category:** Apex, Flow, Process Builder, etc.
* **Log Count:** Number of occurrences
* **Users Impacted:** Unique user count
* **Last Occurred:** Most recent error timestamp
* **Owner:** Assigned person or team

**Using List Views for Triage:**

Many teams use list views as their daily workflow entry point:

1. Open "New Issues" view every morning
2. Sort by Users Impacted (descending)
3. Review top 5 Issues
4. Assign priority and route to appropriate owners

Learn more: [List Views](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/accessing-issues/list-views.md)

### 2. Log-to-Issue Navigation

A powerful feature is navigating from a specific log record to its parent Issue.

**How It Works:**

1. You're viewing a log record (perhaps from a search, report, or alert)
2. Log record has a **Related Issue** field (lookup relationship)
3. Click the Issue name to jump to the Issue's details page
4. From there, see all other logs grouped under this Issue

**Why This Matters:**

Often, you'll first encounter a problem through:

* An alert notification (Slack, email)
* A dashboard showing log spikes
* A user reporting a specific error instance

Following the log to its parent Issue gives you the broader context: How often does this happen? Who else is affected? Has it been triaged?

**Example Workflow:**

```mermaid
graph TD
    A["User calls support: \"I got an error creating an Account\""]
    B[Support searches logs for that user's name]
    C[Finds the log record from 10 minutes ago]
    D[Clicks Related Issue field]
    E[Sees this error has happened 200+ times in last week]
    F[Routes to dev team as high priority]
    A --> B --> C --> D --> E --> F
```

Learn more: [Log-Issue Navigation](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/accessing-issues/log-issue-navigation.md)

### 3. Search

Pharos supports Salesforce global search and advanced search capabilities for Issues.

**Global Search Bar:**\
Type directly in the Salesforce global search:

* Issue names (e.g., "DML Exception: Account")
* Error messages (e.g., "Required field missing")
* Record IDs involved in the error

**Advanced Search Filters:**

* **By Category:** Show only Flow errors, or only Apex errors
* **By Type:** Null pointer exceptions, DML exceptions, validation failures
* **By Date Range:** Issues created or last occurred within specific timeframe
* **By Impact:** Issues affecting more than X users or Y records

**Search Tips:**

* Search for object names (Account, Opportunity) to find Issues affecting those records
* Search for class names or flow names to find related errors
* Use wildcards for partial matches (e.g., "Account\*" finds Account\_Creation, Account\_Update)

Learn more: [Search](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/accessing-issues/search.md)

### 4. Reports and Dashboards

For a higher-level view, Pharos comes with prebuilt (and customizable) reports and dashboards.

**Standard Reports:**

* **Issues by Priority:** Distribution of Highest, High, Medium, Low, Lowest
* **Issues by Functional Area:** Which business areas have most errors
* **Issue Aging:** How long Issues have been open
* **Resolution Velocity:** Time from creation to completion
* **Regression Rate:** Percentage of Issues that reopened after resolution

**Dashboard Use Cases:**

* **Executive Summary:** Total open Issues, trends over time, top impacted areas
* **Triage Dashboard:** New Issues requiring review, prioritized by impact
* **Team Performance:** Resolution metrics by owner or team

**Creating Custom Dashboards:**

You can build dashboards tailored to your workflow:

1. Create report filtering Issues by criteria (e.g., Status = "New", Category = "Apex")
2. Add report to dashboard as a chart (bar, donut, funnel)
3. Schedule dashboard email every morning at 8 AM

**Example: Triage Dashboard Components**

* Chart: Open Issues by Priority (donut chart)
* Table: Top 10 Issues by User Impact (sorted descending)
* Trend: New Issues created per day (line chart, last 30 days)
* Metric: Total Issues closed this sprint

Learn more: [Reports and Dashboards](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/accessing-issues/reports-and-dashboards.md)

## Navigation Workflows by Persona

Different roles navigate Issues in different ways. The workflows below show how admins, developers, managers, and support staff typically move through the tracker.

### Admin/Triage Workflow

**Daily Routine:**

1. Open **New Issues** list view
2. Sort by **Last Occurred** (most recent first)
3. Click into each Issue
4. Review impact metrics
5. Assign Priority and Owner
6. Update Status to **Triaged**

### Developer Workflow

**When Assigned an Issue:**

1. Receive notification (email, Slack)
2. Click link in notification → lands on Issue details page
3. Review debug views (stack trace, error message)
4. Drill into related logs for specific examples
5. Initiate trace if needed
6. Implement fix in sandbox
7. Update Issue Status to **In Progress**, then **In Review**, then **Completed**

### Manager/Team Lead Workflow

**Weekly/Sprint Review:**

1. Open custom **Team Dashboard**
2. Review resolution velocity (trending up or down?)
3. Identify backlog bottlenecks (functional areas with most open Issues)
4. Click through to highest-priority unresolved Issues
5. Reallocate resources as needed
6. Export Issue data to Excel for executive reporting

### Support/User-Facing Workflow

**When User Reports Error:**

1. Search logs for user's name or record ID
2. Find the log from approximate timeframe user mentions
3. Navigate from log to related Issue
4. Check Issue Status:
   * **New/Triaged:** Acknowledge to user, provide workaround if known
   * **Actioned/In Progress:** Give user estimated timeline from dev team
   * **Completed:** Inform user fix is deployed, ask them to retry
5. Add comment on Issue documenting user impact

## Tips for Efficient Navigation

A few standard Salesforce features make everyday navigation faster.

### Use Bookmarks

Bookmark frequently used views:

* Your team's triage view
* High-priority Issues dashboard
* Personal "My Issues" view

### Enable Notifications

Set up Salesforce notifications (or Chatter follows) on:

* Issues assigned to you
* Issues you're collaborating on
* Changes to Issue Status or Priority

### Leverage Quick Actions

From list views, use quick actions to:

* Update Status without opening the Issue
* Change Priority inline
* Bulk assign multiple Issues to a team member

### Pin Important Issues

Use Salesforce's "Pin" feature to keep critical Issues easily accessible:

* Pin to top of your list view
* Pin to your app launcher
* Pin to a custom dashboard

## Mobile Access

Pharos Issues are standard Salesforce objects, so they work on Salesforce Mobile:

* Receive push notifications for Issue assignments
* View Issue details on mobile
* Add comments/photos from field
* Update Status on-the-go

***

{% hint style="success" %}
**Dive Deeper into Each Method:**
{% endhint %}

<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>📋 List Views</strong></td><td>Use standard issue list views and create custom views for your workflow.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/accessing-issues/list-views.md">List Views</a></td></tr><tr><td><strong>📊 Reports and Dashboards</strong></td><td>The homepage dashboard on the issue tab, and the charts available.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/accessing-issues/reports-and-dashboards.md">Reports and Dashboards</a></td></tr><tr><td><strong>🔗 Log-Issue Navigation</strong></td><td>Navigate easily between logs and issues to understand relationships.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/accessing-issues/log-issue-navigation.md">Log-Issue Navigation</a></td></tr><tr><td><strong>🔍 Search</strong></td><td>Find issues using standard Salesforce search functionality.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/accessing-issues/search.md">Search</a></td></tr></tbody></table>
