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

# Collaboration

Learn about collaboration options using native Salesforce features and bugtracker integrations.

Effective Issue resolution requires coordination across teams—developers, admins, QA, product owners, and support. Pharos provides multiple collaboration mechanisms, from native Salesforce features to integrated bug tracking systems.

## Native Salesforce Collaboration

Salesforce provides built-in collaboration on the Issue record through the Chatter feed and the standard Description field, so most teams can coordinate without any extra tooling.

### Chatter Feed

The most immediate collaboration tool is **Salesforce Chatter** on the Issue record.

**How to enable:**

1. Edit the Issue Lightning Page layout
2. Drag **Chatter** component onto the page
3. Recommended placement: Separate tab or bottom right section
4. Save and activate

**What Chatter captures:**

**Automatic Posts:**

* Status changes (New → Triaged → Actioned → Completed)
* Priority changes (Medium → High)
* Assignment changes (Owner field updated)
* Regression detection (Issue reopened after completion)
* Related Issue linkage (when Issues are linked)

**Manual Posts:**

* Comments and notes from team members
* @ mentions to notify specific users
* File attachments (screenshots, logs, data exports)
* Links to related documentation or tickets

### Why Use Chatter

Chatter earns its place for three reasons: it preserves an audit trail, gives newcomers context, and keeps cross-team work transparent.

**Audit Trail:**\
Every decision, discussion, and action is documented chronologically. When you (or someone else) revisit the Issue 6 months later, the full history is preserved.

**Context for Newcomers:**\
New team members assigned to an Issue can read the Chatter feed to understand:

* What's been tried
* Why certain approaches were rejected
* Who to contact for more context

**Cross-Team Transparency:**\
Product owners, support, and engineering can all follow along without needing separate status update meetings.

### Chatter Best Practices

Post at each stage of the lifecycle so the feed tells the full story of the Issue.

**During Triage:**

```
@mention: Assigning to @DanJohnson for investigation
Priority: High - 23 users impacted, daily occurrence
Functional Area: Apex (Opportunity trigger affected)
```

**During Investigation:**

```
Reviewed stack trace. NullPointerException on line 156.
Issue: OpportunityTriggerHandler doesn't null-check 
related Account before accessing Industry field.

Fix: Add null check before line 156.
Deploying to sandbox for testing.
```

**After Fix:**

```
Fix deployed to prod: [Changeset link]
Added null check in OpportunityTriggerHandler.afterInsert
Monitoring for recurrence. Will mark Completed in 1 week if no new logs.
```

**On Regression:**

```
⚠️ Issue regressed! New logs appearing after 30 days dormant.
Recent deployment may have reintroduced bug.
Investigating changeset from [date].
```

## Description Field

If Chatter isn't enabled, use the standard **Description** long-text field on the Issue object.

**Differences from Chatter:**

* Single text field (not chronological feed)
* No @ mentions or file attachments
* Requires manual timestamp/author notation
* Less visibility (no notifications)

**Format suggestion:**

```
[2024-01-15 - Jane Doe]
Triaged as High priority. 23 users impacted daily.
Assigned to Dev Team.

[2024-01-18 - Dan Johnson]
Root cause identified: Missing null check line 156.
Fix deployed via changeset CS-12345.

[2024-01-25 - Jane Doe]
No recurrence in 7 days. Marking Completed.
```

## Bug Tracker Integration

For teams using external issue tracking systems, Pharos integrates with Jira and Azure DevOps.

### Bug Tracker URL Field

The Issue object has a **Bug Tracker URL** field (text/URL).

**Manual workflow:**

1. Create ticket in Jira/Azure DevOps manually
2. Copy ticket URL
3. Paste into Issue's **Bug Tracker URL** field
4. Click field → Opens ticket in new tab

**Automated workflow (with integration):**

1. Click **Create Ticket** button on Issue
2. Pharos automatically creates Jira/ADO ticket
3. Ticket URL auto-populates in Bug Tracker URL field
4. Inline view of ticket appears on Issue page

### Inline Ticket View

When Bug Tracker URL is populated and integration is active:

**What you'll see:**

* Ticket status (Open, In Progress, Resolved, Closed)
* Ticket title and description
* Assignee
* Comments from bug tracker
* Last updated timestamp

**Benefits:**

* No need to leave Salesforce to check ticket status
* Single pane of glass for Issue + Ticket
* Real-time sync (depending on integration config)

### Bidirectional Sync

Advanced integrations support two-way status updates:

**Salesforce → Bug Tracker:**

* Issue status changes → Ticket status updates
* Issue priority changes → Ticket priority updates
* Comments added → Comments synced to ticket

**Bug Tracker → Salesforce:**

* Ticket marked "Resolved" → Issue status → `Completed`
* Ticket assignee changed → Issue owner updated
* Ticket comments → Synced to Issue Chatter/Comments

### Integration Setup

Contact your Pharos admin or see:

* [Jira Integration](https://docs.pharos.ai/configuration-guide/integrations/jira.md)
* [Azure DevOps Integration](https://docs.pharos.ai/configuration-guide/integrations/azure.md)

## Assignment and Ownership

### Owner Field

Every Issue has an **Owner** (standard Salesforce field).

**Default:** Creator (usually the Pharos system user) **Updated during triage:** Assigned to specific developer or team

**Use Owner for:**

* Routing Issues to appropriate team members
* Filtering list views (My Issues = Owner = Me)
* Accountability tracking (who's responsible for resolution)

**Tip:** Use Salesforce **Queue** as Owner for team-based assignment:

* Create Queue: "Apex Dev Team"
* Assign Issue Owner = Apex Dev Team Queue
* Team members pick from queue

### Assignment Notifications

Set up Salesforce **Workflow Rules** or **Process Builder** to notify on assignment:

**Trigger:** Issue Owner changed **Action:** Send email to new Owner **Email template:** Include Issue link, priority, summary

Or use Pharos **Notification Rules** (if available):

* Send Slack DM when Issue assigned
* Post to team channel with @ mention
* Include impact metrics and debug view link

## Cross-Team Collaboration Patterns

These patterns show how support, product, engineering, and QA hand work back and forth through the Issue record.

### Support → Engineering

**Scenario:** Support receives user complaint about error.

**Workflow:**

1. Support searches Pharos logs for user's error
2. Finds log, navigates to related Issue
3. Adds Chatter comment documenting user impact:

   ```
   User John Smith called support. Error blocks his workflow.
   Account ID: 001xx000003ABCD
   Workaround: Advised to populate Industry field before saving.
   ```
4. @ mentions dev team in Chatter
5. Engineering investigates and responds with ETA

### Product → Engineering

**Scenario:** Product manager prioritizes Issues by business value.

**Workflow:**

1. Product reviews high-impact Issues weekly
2. Adds Chatter comment with business context:

   ```
   This affects Opportunity pipeline visibility for sales.
   Top priority for Q1. Escalating to High.
   ```
3. Changes Priority → High
4. @ mentions engineering lead
5. Engineering allocates resources accordingly

### Engineering → QA

**Scenario:** Fix deployed, needs verification.

**Workflow:**

1. Developer deploys fix, updates Issue status → `In Review`
2. Adds Chatter comment:

   ```
   Fix deployed: Changeset CS-12345
   Summary: Added null check OpportunityTriggerHandler line 156
   @QATeam: Please verify in sandbox before marking Completed.
   ```
3. QA tests, adds Chatter comment:

   ```
   Verified in sandbox. Tested with 50 Accounts (some with blank Industry).
   No errors. Looks good. ✅
   ```
4. Developer marks Issue → `Completed`

## Collaboration via Reports and Dashboards

### Team Dashboards

Create shared dashboards for visibility:

**Executive Dashboard:**

* Total open Issues (metric)
* Issues by Priority (donut chart)
* Weekly Issue trend (line chart)
* Top 10 Issues by User Impact (table)

**Dev Team Dashboard:**

* My Open Issues (filtered report)
* Issues Actioned This Sprint (status filter)
* Average Time to Resolution (formula)
* Regression Rate (% reopened)

**Support Dashboard:**

* New Issues Today (real-time)
* Issues by Functional Area (filter by Apex vs. Flow vs. Process Builder)
* Unassigned Issues needing triage
* Issues with recent user comments

### Scheduled Reports

Email weekly summaries:

* All High/Highest open Issues → Engineering lead
* New Issues requiring triage → Admin team
* Completed Issues this week → Product manager

## Mobile Collaboration

Pharos Issues are standard Salesforce objects, so mobile collaboration works natively:

**Salesforce Mobile App:**

* Receive push notifications (Issue assigned, status changed)
* View Issue details
* Add Chatter comments
* Update Status or Priority
* Attach photos from field (if relevant)

**Use cases:**

* On-call engineer gets paged → Views Issue on phone → Triages from mobile
* Support agent at customer site → Documents error → Adds photo of screen
* Manager reviewing open Issues → Updates priorities → @ mentions team

## Collaboration Tools Summary

The table below compares the available collaboration tools and where each one fits best.

| Tool                   | Best For                                      | Limitations                              |
| ---------------------- | --------------------------------------------- | ---------------------------------------- |
| **Chatter**            | Real-time discussion, audit trail, @ mentions | Requires setup, not all orgs use Chatter |
| **Description Field**  | Simple notes, low setup                       | No notifications, manual timestamping    |
| **Bug Tracker URL**    | Linking to external tickets                   | Manual (unless integration active)       |
| **Inline Ticket View** | Unified view of Issue + Ticket                | Requires integration setup               |
| **Owner Field**        | Assignment and routing                        | Single owner only (no co-ownership)      |
| **Dashboards**         | Team visibility and metrics                   | Read-only, not interactive               |
| **Mobile**             | On-the-go updates                             | Limited functionality vs. desktop        |

## Best Practices

### Establish Communication Norms

**Define standards for your team:**

* Always comment when changing Status
* @ mention when assigning to someone
* Document triage reasoning (why High vs. Medium)
* Link to changesets/PRs when deploying fixes

### Use Templates

Create comment templates for consistency:

**Triage Template:**

```
Priority: [High/Medium/Low]
Reasoning: [User count, data impact, business criticality]
Assigned to: [@Person]
Next action: [Investigation/Fix/Monitor]
```

**Resolution Template:**

```
Fix deployed: [Date]
Changeset/PR: [Link]
Summary: [What was fixed]
Monitoring period: [1 week/2 weeks]
Expected completion: [Date]
```

### Review Collaboration History

Before starting work on an Issue:

1. Read full Chatter feed
2. Check if related Issues have relevant discussion
3. See if workarounds have been documented
4. Understand what's been tried and why it didn't work

{% hint style="success" %}
**Next Steps:**

* [Actioning](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/issue-lifecycle/actioning.md) – Creating tickets and integrating with bug trackers
* [Triaging](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/issue-lifecycle/triaging.md) – Systematic review and prioritization
* [Issue Details Overview](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/issue-details.md) – See full Issue details page structure
  {% endhint %}
