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

# Issue Details

Explore the comprehensive groups of data presented on the issue details page.

The Issue details page is your command center for understanding, prioritizing, and resolving errors. It aggregates metrics, visualizations, and debugging information from potentially thousands of logs into a single, actionable view.

{% hint style="success" %}
**One Issue, Complete Context:** All the data you need to understand, prioritize, and resolve an error pattern—from aggregate impact metrics to individual log occurrences—in a single Lightning page.
{% endhint %}

## Overview

Every Issue record provides a comprehensive set of information organized into logical sections. This page introduces the key components and how they work together to support your troubleshooting workflow.

## Page Layout

The Issue details page is structured to support different personas and workflows:

### Top Section: Status and Actions

Critical information for quick decision-making:

* **Issue Identity:** Category, Type, Functional Area
* **Lifecycle:** Status, Priority, Owner, Regression flag
* **Quick Actions:** Bug Tracker integration, Ticket creation, Trace initiation

### Middle Section: Impact Metrics

Quantified measurements help you understand severity:

* [**Occurrence Information**](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/issue-details/occurrence-info.md) → When and how often this happens
* [**Impact Statistics**](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/issue-details/impact-statistics.md) → Who and what is affected

### Left Sidebar: Visualizations

Graphical representations reveal patterns at a glance:

* Occurrence charts (timeline views)
* User impact distribution (donut charts)
* Data impact distribution (object breakdowns)

### Center Section: Technical Details

Information needed for root cause analysis:

* [**Debug Views**](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/issue-details/debug-views.md) → Stack traces, flow paths, error messages
* [**Related Logs**](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/issue-details/related-logs.md) → Individual log occurrences with record-level detail
* [**Issue Relationships**](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/issue-details/issue-relationships.md) → Related and duplicate Issues

### Right Sidebar: Collaboration

Tools for team coordination:

* [**Collaboration**](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/issue-details/collaboration.md) → Chatter feed, comments, bug tracker integration
* [**AI Analysis**](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/issue-details/ai-analysis.md) → Root cause suggestions and recommendations
* [**Org Genie**](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/issue-details/org-genie.md) → Natural language assistant for Issue questions
* [**Tracing**](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/issue-details/tracing.md) → Active trace schedules and captured debug logs

## Key Concepts

A few core concepts underpin everything on the page, starting with the relationship between Issues and Logs.

{% hint style="info" %}
**Understanding the Fundamentals**

The Issue details page brings together multiple data sources and perspectives. Grasping the relationship between Issues and Logs is essential for effective troubleshooting.
{% endhint %}

### Issues vs. Logs

Understanding the distinction is fundamental:

| Aspect         | Log Record                        | Issue Record                      |
| -------------- | --------------------------------- | --------------------------------- |
| **Represents** | Single error occurrence           | Pattern of related errors         |
| **Creation**   | One per failure                   | One per unique error pattern      |
| **Metrics**    | Specific user, timestamp, records | Aggregate frequency, total impact |
| **Purpose**    | Record individual event           | Track and resolve root cause      |

**Think of it this way:** You don't fix 3,000 logs—you fix one Issue. When resolved, all those logs stop occurring.

### Aggregate vs. Specific

The Issue page balances two views:

**Aggregate View (Issue-level):**

* Total users impacted across all occurrences
* Average frequency and daily volume
* Trends over time
* Stack trace from first occurrence

**Specific View (Log-level):**

* Drill into individual logs via Related Logs
* See specific user, timestamp, record IDs
* Investigate data patterns

Both views are essential—aggregates for prioritization, specifics for investigation.

## Common Workflows

The page supports several everyday workflows, from triaging a new Issue to collaborating on a fix.

### Workflow 1: Triage New Issue

```
1. Review Occurrence Info → How often is this happening?
2. Check Impact Statistics → How many users/records affected?
3. Review Debug View → What type of error?
4. Assign Priority based on metrics
5. Update Status to "Triaged"
6. Add comment documenting decision
```

**Time:** 2-5 minutes per Issue

### Workflow 2: Investigate for Resolution

```
1. Review Debug Views → Read stack trace/flow path
2. Check Related Logs → Find recent specific occurrences
3. Open specific log → See record IDs and user context
4. Navigate to affected records → Check data patterns
5. Initiate Trace (if needed) → Capture full debug logs
6. Implement fix in sandbox
7. Deploy and monitor
```

**Time:** Hours to days, depending on complexity

### Workflow 3: Create External Ticket

```
1. Review Impact Statistics → Document users and data affected
2. Copy Debug View info → Stack trace and error details
3. Check Related Issues → Link to related problems
4. Click "Create Ticket" → Jira/ADO integration
5. Ticket created with Issue details pre-populated
6. Update Issue Status to "Actioned"
```

**Time:** 2-3 minutes with integration

### Workflow 4: Collaboration

```
1. User reports error → Support finds log, navigates to Issue
2. Support adds Chatter comment → Documents user context
3. @ mentions developer → Notifies assigned team
4. Developer investigates → Adds findings to Chatter
5. Fix deployed → Developer documents fix and changeset
6. QA verifies → Adds verification comment
7. Issue marked Completed → Full audit trail preserved
```

**Time:** Varies, but all context in one place

## Customization Options

Because the Issue details page is a Lightning page, you can adapt it to your team's processes.

{% hint style="info" %}
**Tailor to Your Workflow**

The Issue details page is highly customizable as a Lightning Page. Adapt the layout, add components, and create custom fields to match your team's unique processes.
{% endhint %}

The Issue details page is a Lightning Page, allowing customization:

### Adding Components

**Chatter Feed:**

1. Edit Issue Lightning Page
2. Drag Chatter component to desired location
3. Save and activate

**Custom Components:**

* Reports showing related Issues
* Dashboards with team metrics
* Custom visualizations

### Rearranging Layout

Modify to match your workflow:

* Move high-priority sections higher
* Hide unused components (e.g., AI Analysis if not licensed)
* Create separate tabs for different personas

### Adding Custom Fields

Extend the Issue object:

* **Root Cause Category** (picklist for reporting)
* **Business Owner** (lookup for stakeholder tracking)
* **Estimated Hours** (number for effort tracking)
* **Severity Score** (formula combining impact metrics)

## Using Issue Details by Persona

Different roles lean on different parts of the page, from impact metrics for admins to stack traces for developers.

### Admin/Business Analyst

**Focus on:**

* Impact metrics (user count, record count)
* Occurrence patterns (daily? one-time?)
* Priority assignment based on business impact

**Less focus on:**

* Deep technical stack traces
* Code-level debugging

**Actions:**

* Triage and prioritize
* Route to appropriate teams
* Document business context

### Developer

**Focus on:**

* Debug views (stack traces, error messages)
* Related logs (specific test cases)
* Tracing (full debug log context)

**Less focus on:**

* Aggregate metrics (rely on triage priority)

**Actions:**

* Investigate root cause
* Implement fix
* Document technical resolution

### Manager/Team Lead

**Focus on:**

* Trends (occurrence chart)
* Distribution (which functional areas)
* Resolution velocity (time in each status)

**Less focus on:**

* Individual Issue details
* Code-level debugging

**Actions:**

* Resource allocation
* Process improvements
* Executive reporting

### Support/User-Facing

**Focus on:**

* Related logs (find user's specific occurrence)
* Impact statistics (who else affected?)
* Collaboration (document user reports)

**Less focus on:**

* Technical debugging
* Code changes

**Actions:**

* Find user's specific error
* Provide workarounds
* Escalate to engineering

## Data Refresh and Real-Time Updates

### When Data Updates

**Real-time:**

* New logs arrive → Log count increments
* User comments added → Chatter feed updates
* Status changed → History tracked

**Near real-time (minutes):**

* Impact metrics recalculated
* Occurrence charts updated
* Related Issue relationships computed

**Batch (hourly/daily):**

* AI Analysis suggestions refreshed
* Aggregate statistics recalculated
* Trend indicators updated

### Refreshing the Page

If you keep an Issue page open for extended periods:

* Browser refresh → See latest data
* Lightning page auto-refreshes some components
* Chatter feed updates automatically (if polling enabled)

## Performance Considerations

Very large or long-running Issues need a little extra care to stay responsive.

{% hint style="warning" %}
**Managing High-Volume Issues**

Issues with tens of thousands of logs require special handling. Use filters and date ranges to focus on relevant data, and consider archiving very old logs to maintain performance.
{% endhint %}

### Large Issues (10,000+ logs)

Issues with very high log counts:

* Related Logs list paginates automatically
* Use filters to narrow down (date range, user)
* Impact charts may show "Last 30 days" by default

### Long-Running Issues

Issues open for months/years:

* Occurrence chart at 6-month zoom for full view
* Consider archiving very old logs
* Focus on recent activity for current investigation

## Mobile Access

Issue details are accessible on Salesforce Mobile:

* View all metrics and charts
* Add Chatter comments
* Update Status and Priority
* View debug information
* Limited tracing capabilities (view only, not create)

***

## Explore Each Section in Detail

### Metrics and Impact

<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>📅 Occurrence Info</strong></td><td>Occurrence charts and occurrence time statistics presented on the issue details page.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/issue-details/occurrence-info.md">Occurrence Info</a></td></tr><tr><td><strong>📊 Impact Statistics</strong></td><td>User and data impact charts, with overall metrics for prioritization.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/issue-details/impact-statistics.md">Impact Statistics</a></td></tr></tbody></table>

### Technical Investigation

<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>🐛 Debug Views</strong></td><td>Debug views from the issue record, with references to log debug views.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/issue-details/debug-views.md">Debug Views</a></td></tr><tr><td><strong>📝 Related Logs</strong></td><td>View and navigate to related logs from the issue details page.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/issue-details/related-logs.md">Related Logs</a></td></tr><tr><td><strong>🔗 Issue Relationships</strong></td><td>The two different types of issue relationships: related issues and duplicates.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/issue-details/issue-relationships.md">Issue Relationships</a></td></tr></tbody></table>

### Collaboration and Tools

<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>💬 Collaboration</strong></td><td>Collaboration options using native Salesforce features and bugtracker integrations.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/issue-details/collaboration.md">Collaboration</a></td></tr><tr><td><strong>🤖 AI Analysis</strong></td><td>AI analysis functionality for root cause identification and remediation suggestions.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/issue-details/ai-analysis.md">AI Analysis</a></td></tr><tr><td><strong>🧞 Org Genie (Issue Level)</strong></td><td>AI-powered conversational queries to investigate specific issues and their root causes.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/issue-details/org-genie.md">Org Genie</a></td></tr><tr><td><strong>🔬 Tracing</strong></td><td>The tracing process for dynamically fetching and analyzing Salesforce debug logs.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/issue-details/tracing.md">Tracing</a></td></tr></tbody></table>
