> 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/configuration-guide/ticketing/actions.md).

# Actions

Configure ticketing actions that define how tickets are created and commented in Jira or Azure DevOps.

Ticketing actions are reusable templates that define **how** tickets are created—project, issue type, priority mapping, description format, and labels. Think of them as bug templates: you configure an action once, then use it from the Create Ticket button or from ticketing rules.

{% hint style="info" %}
For action concepts and design, see [Ticketing Actions](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/ticketing-and-bugtracking/issue-level-ticketing/ticketing-actions.md).
{% endhint %}

***

## Accessing Ticketing Actions

1. Open the **Pharos** app
2. Navigate to **Pharos Admin**
3. Select **Ticketing** from the left-hand menu
4. Click **Actions**

Actions are organized by tab — **Logs** and **Issues**:

![Ticketing Actions — Logs tab showing 4 configured actions with Name, Project, Type, Subject, Used In Rules, and Created By columns](https://4264222071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdl9tmJ56lvwg5XY63QYr%2Fuploads%2Fgit-blob-80bb471e046294f7c325d68cd07c8d3aa52be0b2%2Fticketing-actions-logs-tab.png?alt=media)

![Ticketing Actions — Issues tab with Action Type filter (Create / Update) and 6 configured actions](https://4264222071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdl9tmJ56lvwg5XY63QYr%2Fuploads%2Fgit-blob-831cb31777a9ecd18af58f69140d14f4a1ee716f%2Fticketing-actions-issues-tab.png?alt=media)

Use the **Ticketing System** dropdown to filter by integration (Jira, Azure DevOps, or All), and the **Action Type** dropdown to filter by Create or Update.

***

## Actions vs. Rules

| Concept    | Purpose                                                                    |
| ---------- | -------------------------------------------------------------------------- |
| **Action** | *What* to do — project, issue type, description template, priority mapping |
| **Rule**   | *When* to do it — filter criteria and trigger (create vs. update)          |

Actions are invoked by:

* **Manual:** Create Ticket button on an issue → select action from dropdown
* **Automated:** Ticketing rule matches → rule invokes the configured action

***

## Action Types

| Type              | Description                                        | Use                                                       |
| ----------------- | -------------------------------------------------- | --------------------------------------------------------- |
| **Create ticket** | Create a new Jira ticket or Azure DevOps work item | New issues, hot issues, status-based escalation           |
| **Add comment**   | Add a comment to an existing ticket                | Update rules when issue becomes hot or crosses thresholds |

Comment actions only apply to **update rules** and only work when the issue already has a linked ticket.

When creating an action, the **Send action to** dropdown lists the available ticketing system types:

![Action type dropdown showing Jira Ticket and Azure Dev Ops Work Item](https://4264222071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdl9tmJ56lvwg5XY63QYr%2Fuploads%2Fgit-blob-9e74d973d852261038443b0cc73cff4f82f574d9%2Fticketing-action-type-dropdown.png?alt=media)

***

## Creating a Ticketing Action

1. In Ticketing → Actions, click **Add New Action**
2. Select the action type from the **Send action to** dropdown (e.g., **Jira Ticket**, **Azure Dev Ops Work Item**, or **JIRA Ticket Comment**)
3. Fill in the required fields and configure:

### For Create Ticket Actions

The Jira Ticket form includes fields for Project, Type, Priority, Assignee, Components, Epic, Labels, Subject (ticket title), and Message (ticket body). Click **More Jira Fields** at the bottom to expose additional fields. Use the **Insert Field** button to browse and insert merge fields.

![Jira Ticket create action form — showing Project, Type, Priority, Assignee, Components, Epic, Labels, Subject, and Message fields with merge field syntax](https://4264222071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdl9tmJ56lvwg5XY63QYr%2Fuploads%2Fgit-blob-76c5974e55b89529145bf1dcd1131e193037d4d1%2Fticketing-action-jira-form.png?alt=media)

| Field          | Description                                                                     |
| -------------- | ------------------------------------------------------------------------------- |
| **Project**    | Jira project or Azure DevOps project                                            |
| **Type**       | Bug, Story, Task, Issue, etc.                                                   |
| **Priority**   | Default or map from Pharos priority                                             |
| **Assignee**   | Optionally assign to a team member                                              |
| **Components** | Jira components (e.g., `TComponent1`)                                           |
| **Epic**       | Link to a Jira epic (e.g., `PTP-503 Test Epic 1`)                               |
| **Labels**     | Comma-separated labels (e.g., `pharos-issues`)                                  |
| **Subject**    | Ticket title; use merge fields (e.g., `{!pharos__Issue__c.pharos__Summary__c}`) |
| **Message**    | Ticket body; use merge fields for links, error details, impact                  |

### For Comment Actions

Comment actions have a simpler form — just the **Message** field with the **Insert Field** button:

![JIRA Ticket Comment action form — Message field with merge fields for issue link and log count](https://4264222071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdl9tmJ56lvwg5XY63QYr%2Fuploads%2Fgit-blob-8e32089d85b380de52234e37218553a9c6433e1b%2Fticketing-action-jira-comment.png?alt=media)

| Field       | Description                                                                                                      |
| ----------- | ---------------------------------------------------------------------------------------------------------------- |
| **Message** | Comment text; use merge fields (e.g., `{!pharos__Issue__c.Link}` and `{!pharos__Issue__c.pharos__Log_Count__c}`) |

***

## Merge Fields

Use merge fields to dynamically populate ticket content from the Pharos issue. Click the **Insert field** button in the template editor to browse and insert available fields.

### Common Merge Fields

| Field                                              | Description                                |
| -------------------------------------------------- | ------------------------------------------ |
| `{!pharos__Issue__c.pharos__Summary__c}`           | Issue summary / error headline             |
| `{!pharos__Issue__c.pharos__Description__c}`       | Error description text                     |
| `{!pharos__Issue__c.pharos__Log_Count__c}`         | Total occurrence count                     |
| `{!pharos__Issue__c.pharos__Impacted_Users__c}`    | Unique users affected                      |
| `{!pharos__Issue__c.Link}`                         | Direct link back to the Pharos issue       |
| `{!pharos__Issue__c.pharos__Average_Frequency__c}` | Average number of days between occurrences |
| `{!pharos__Issue__c.pharos__Status__c}`            | Current issue status                       |
| `{!pharos__Issue__c.pharos__Functional_Area__c}`   | Functional area assignment                 |
| `{!pharos__Issue__c.pharos__Category__c}`          | Issue category                             |

{% hint style="info" %}
The field names use the Pharos managed package namespace (`pharos__`). Use the **Insert Field** button in the action editor to browse and insert available fields — this avoids typos and shows every field on the Issue or Log object.
{% endhint %}

***

## Customizing Subject and Description

### Subject (Summary / Title)

The default subject template may include prefixes like "New Issue" or the organization name. Trim these to keep ticket titles concise and scannable in your backlog:

| Default                                                           | Recommended                              |
| ----------------------------------------------------------------- | ---------------------------------------- |
| `New Issue - [Org Name] - {!pharos__Issue__c.pharos__Summary__c}` | `{!pharos__Issue__c.pharos__Summary__c}` |

### Description

Build the ticket body with a mix of merge fields and static text. A good description gives the developer everything they need without switching back to Pharos:

```
{!pharos__Issue__c.Link}

Details: {!pharos__Issue__c.pharos__Description__c}

Impact:
- Users Impacted: {!pharos__Issue__c.pharos__Impacted_Users__c}
- Occurrences: {!pharos__Issue__c.pharos__Log_Count__c}
- Frequency: {!pharos__Issue__c.pharos__Average_Frequency__c} days
```

{% hint style="info" %}
Keep descriptions focused on context the developer needs. The Pharos link gives them access to full stack traces and log history — no need to duplicate everything in the ticket body.
{% endhint %}

***

## Template Examples

### Jira — Production Bug

```
Name:        Production Bug
Integration: Jira Ticket
Project:     Engineering (ENG)
Type:        Bug
Priority:    High
Labels:      pharos-issues, Production
Epic:        (optional — link to a tracking epic)
Components:  (optional — e.g., "TComponent1")
Subject:     {!pharos__Issue__c.pharos__Summary__c}
Message:
  {!pharos__Issue__c.Link}

  Details: {!pharos__Issue__c.pharos__Description__c}

  Impact: {!pharos__Issue__c.pharos__Impacted_Users__c} users,
          {!pharos__Issue__c.pharos__Log_Count__c} occurrences
```

### Azure DevOps — Production Bug

```
Name:        Production Bug
Integration: Azure Dev Ops Work Item
Project:     MyProject
Type:        Bug
Priority:    2
Tags:        Pharos, Production
Area Path:   MyProject\Backend
Iteration:   (current sprint or backlog)
Subject:     {!pharos__Issue__c.pharos__Summary__c}
Message:
  {!pharos__Issue__c.Link}

  Details: {!pharos__Issue__c.pharos__Description__c}

  Impact: {!pharos__Issue__c.pharos__Impacted_Users__c} users,
          {!pharos__Issue__c.pharos__Log_Count__c} occurrences
```

{% hint style="info" %}
Jira uses **Epic**, **Components**, and **Labels**. Azure DevOps uses **Area Path**, **Iteration**, and **Tags**. The rest of the template is identical.
{% endhint %}

***

## Template Strategy

Create multiple actions to handle different scenarios:

| Action                      | Purpose                                                                                                                                                                     |
| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Production Bug**          | General production issues — Bug type, medium priority                                                                                                                       |
| **Critical Production Bug** | High-urgency issues — Bug type, highest priority, may trigger additional labels or assignments                                                                              |
| **Sandbox Issue**           | Non-production environments — Task type, low priority, `Sandbox` label                                                                                                      |
| **Hot Issue Comment**       | Add comment when issue crosses threshold (e.g., "This issue has now occurred a total of {!pharos\_\_Issue\_\_c.pharos\_\_Log\_Count\_\_c} times. Please investigate asap!") |

{% hint style="info" %}
Different environments and severity levels often need different projects, issue types, or labels. Creating dedicated actions keeps each template simple and reduces the chance of routing tickets to the wrong board.
{% endhint %}

### Labeling Convention

Use consistent labels or tags to make Pharos-created tickets easy to filter:

* Always include a **Pharos** label / tag
* Add environment labels: `Production`, `Sandbox`, `UAT`
* Consider functional area labels: `Sales`, `Service`, `Integration`

***

## Using Actions in Rules

When configuring a [ticketing rule](https://docs.pharos.ai/configuration-guide/ticketing/rules.md):

1. In the **Actions** section of the rule, click **Add New** or **Add Existing**
2. Select the ticketing system (Jira Ticket, Azure Dev Ops Work Item, or their comment variants)
3. Configure or select the action template
4. The rule invokes that action when its filter criteria match

Multiple rules can reference the same action. Updating an action updates all rules that use it.

{% hint style="info" %}
An action that is referenced by one or more rules cannot be deleted. The delete icon will show a tooltip explaining the dependency:

<img src="https://4264222071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdl9tmJ56lvwg5XY63QYr%2Fuploads%2Fgit-blob-9b7cd299f8d330ddb1a6fcdffab733260988d771%2Fticketing-action-delete-tooltip.png?alt=media" alt="Tooltip: &#x22;This action cannot be deleted as it&#x27;s referenced by at least one ticketing rule&#x22;" data-size="original">

Remove the action from all rules first, then delete.
{% endhint %}

***

## Troubleshooting

| Issue                                        | Cause                             | Resolution                                                      |
| -------------------------------------------- | --------------------------------- | --------------------------------------------------------------- |
| Action not visible in Create Ticket dropdown | Action not configured or inactive | Verify action exists and is active                              |
| Wrong project or issue type                  | Action misconfigured              | Edit the action; project/type are set in the action             |
| Ticket missing context                       | Description template incomplete   | Add merge fields for error message, impact, Pharos link         |
| Comment not appearing                        | Issue has no ticket               | Comment actions require an existing ticket; create ticket first |

***

## Related

* [Rules](https://docs.pharos.ai/configuration-guide/ticketing/rules.md) — When tickets are created
* [Jira Authentication](https://docs.pharos.ai/configuration-guide/integrations/jira/authentication.md) — Jira connection setup
* [Jira Defaults](https://docs.pharos.ai/configuration-guide/integrations/jira/defaults.md) — Default project, issue type, components
* [Azure DevOps Authentication](https://docs.pharos.ai/configuration-guide/integrations/azure/authentication.md) — Azure DevOps connection setup
* [Azure DevOps Defaults](https://docs.pharos.ai/configuration-guide/integrations/azure/defaults.md) — Default project, work item type, area path
* [Manual Ticket Creation](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/ticketing-and-bugtracking/issue-level-ticketing/manual-ticket-creation.md) — Using actions from the Create Ticket button
