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

# Ticketing

Configure ticketing rules and actions in Pharos Admin for automated bug tracking.

Ticketing in Pharos connects issues and logs to your bug tracker — Jira or Azure DevOps. You define **rules** that decide *when* to create tickets, and **actions** that decide *how* tickets look (project, type, description template). Together they automate the flow from error detection to developer backlog.

{% hint style="info" %}
For conceptual details on how ticketing works in Pharos, see [Ticketing and Bugtracking](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/ticketing-and-bugtracking.md).
{% endhint %}

***

## In This Section

<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>📐 Rules</strong></td><td>Define when tickets are created — filter criteria, execution order, and phased automation.</td><td><a href="https://docs.pharos.ai/configuration-guide/ticketing/rules.md">Rules</a></td></tr><tr><td><strong>🎬 Actions</strong></td><td>Define how tickets look — project, issue type, priority, and reusable templates.</td><td><a href="https://docs.pharos.ai/configuration-guide/ticketing/actions.md">Actions</a></td></tr></tbody></table>

***

## Manual Ticket Creation

Before automating with rules, most teams start by creating tickets manually from the issue detail page.

1. Open a Pharos issue
2. Click **Create Ticket** at the top of the issue page
3. Choose your creation method:

**Use Existing Action** — select a saved [ticketing action](https://docs.pharos.ai/configuration-guide/ticketing/actions.md) from the dropdown. The template fields (project, issue type, description) pre-populate. Make any adjustments, then click **Create**.

**Create New** — fill out the ticket form from scratch. Optionally save it as a new action for future use, then click **Create**.

Once the ticket is created:

* A link is established between the Pharos issue and the ticket
* Ticket information appears in the **Bug Tracker** section of the issue
* Bidirectional navigation is enabled — click links to jump between systems

{% hint style="info" %}
Manual creation is the recommended starting point. Triage issues first — assign priority, add comments — and only create tickets for items that warrant development work. See [Rules](https://docs.pharos.ai/configuration-guide/ticketing/rules.md) for guidance on graduating to automation.
{% endhint %}

***

## Ticket Synchronization

### What Syncs

Synchronization is selective, and each behavior is a separate toggle on the [Jira](https://docs.pharos.ai/configuration-guide/integrations/jira/defaults.md) or [Azure DevOps](https://docs.pharos.ai/configuration-guide/integrations/azure/defaults.md) Defaults screen:

* **Completed status** — marking a Jira ticket Done/Closed (or resolving an Azure DevOps work item) sets the Pharos issue to **Completed** and stamps **Resolved On** on the issue
* **Priority** — in either direction, or both. With both enabled the bugtracker wins: once priority syncs inbound, it keeps overriding priority set directly on the issue
* **Related and duplicate links** — linking two tickets links the corresponding issues, and vice versa

Status sync is completion-only. Moving a ticket to *In Progress* does not change the Pharos issue status, and Jira comments and assignee changes do not flow into Pharos.

### Reoccurrence Handling

If an issue reoccurs after its linked ticket was completed:

1. Pharos **returns the issue to New** status, sets **Regressed On**, clears **Resolved On**, and flags it as a regression. This also applies to duplicates of completed issues
2. Pharos **creates a new ticket** for the new occurrence
3. The new ticket is **linked to the previous ticket** (Jira uses related-issue links; Azure DevOps uses related work-item links)
4. This avoids problems with closed sprints, completed release cycles, and historical metrics

{% hint style="info" %}
Creating a new ticket instead of reopening the old one keeps your sprint boards clean and preserves the historical record. The link between old and new tickets maintains full context.
{% endhint %}

***

## When NOT to Create Tickets

Not every issue warrants a ticket:

* **Low priority issues** — mark as triaged with comments but don't create tickets
* **Duplicates** — close as duplicate instead of creating redundant tickets
* **Resolved issues** — if the issue hasn't occurred recently, it may have self-resolved
* **Data issues** — some issues are one-time data problems rather than code defects

***

{% hint style="info" %}
**Related:** [Integrations](https://docs.pharos.ai/configuration-guide/integrations.md) — Jira and Azure DevOps setup · [Ticketing and Bugtracking](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/ticketing-and-bugtracking.md) — Bidirectional sync, regression detection, ticket content
{% endhint %}
