> 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/integrations/jira/defaults.md).

# Defaults

Configure default synchronization and ticket behavior for the Jira integration.

The Defaults page controls how Pharos synchronizes data between Jira tickets and Pharos issues/logs. Settings are split into two tabs — **Logs** and **Issues** — each governing different aspects of the integration behavior.

{% hint style="info" %}
For ticket template configuration (project, issue type, description, merge fields), see [Ticketing Actions](https://docs.pharos.ai/configuration-guide/ticketing/actions.md). Defaults controls synchronization behavior, not template content.
{% endhint %}

***

## Accessing Defaults Settings

1. Open the **Pharos** app
2. Navigate to **Pharos Admin** → **Integrations** → **Jira**
3. Select the **Defaults** sub-section

***

## Logs Tab

The Logs tab controls how Pharos handles Jira tickets created from log-level ticketing rules.

![Jira Defaults — Logs tab showing three controls: Auto Generate Similarity Labels, Auto Relate Tickets With Similar Errors, Create Unique Tickets by Org](https://4264222071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdl9tmJ56lvwg5XY63QYr%2Fuploads%2Fgit-blob-2c41fe9a11b2dabfff8c4b7b3adabf182623e7a0%2Fjira-defaults-logs-tab.png?alt=media)

| Control                                             | Description                                                                                                                                                                                                             |
| --------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Auto Generate Similarity Labels in Jira Tickets** | When enabled, Pharos adds generated labels to new Jira tickets that can be used to search for same or similar issues. New labels are appended to your existing labels or any defaults defined in the ticketing action.  |
| **Auto Relate Tickets With Similar Errors**         | When enabled, Pharos automatically relates similar issues via a Jira link. The links point to the earliest created unresolved similar issue.                                                                            |
| **Create Unique Tickets by Org**                    | When enabled, Pharos always creates a new ticket even if an open ticket for the same error from a different org already exists. Useful for multi-org (Connected Orgs) setups where each org should have its own ticket. |

{% hint style="info" %}
These controls are most relevant for organizations using **log-level ticketing rules** or **Connected Orgs**. If you only create tickets at the issue level, the Issues tab is more important.
{% endhint %}

***

## Issues Tab

The Issues tab controls bidirectional synchronization between Jira tickets and Pharos issues.

![Jira Defaults — Issues tab showing five synchronization controls: related tickets, duplicate tickets, ticket priority, issue priority, and completed status](https://4264222071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdl9tmJ56lvwg5XY63QYr%2Fuploads%2Fgit-blob-9a25c9c74e61865786b692f4619f3a9bbee98529%2Fjira-defaults-issues-tab.png?alt=media)

### Relationship Sync

| Control                                      | Description                                                                                                                                                                                        |
| -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Synchronize related tickets and Issues**   | When enabled, Pharos automatically relates Jira tickets corresponding to related issues, and vice versa — will relate issues when Jira tickets are linked.                                         |
| **Synchronize duplicate tickets and Issues** | When enabled, Pharos automatically creates a duplicate link for Jira tickets corresponding to duplicate issues, and vice versa — will duplicate issues when Jira tickets are linked as duplicates. |

### Priority Sync

| Control                                  | Description                                                                                                                                                                                                                   |
| ---------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Automatically update ticket priority** | When enabled, Pharos updates the Jira ticket priority based on the corresponding issue priority. Changes in Pharos flow to Jira.                                                                                              |
| **Automatically update Issue priority**  | When enabled, Pharos updates the issue priority based on the corresponding Jira ticket priority. Once updated, Pharos always synchronizes priority from the Jira ticket, overriding any direct priority updates on the issue. |

{% hint style="warning" %}
Enabling both priority sync directions creates a bidirectional sync. If you update priority in Jira, it flows to Pharos. If you update in Pharos, it flows to Jira. Be aware that the Jira-to-Pharos direction takes precedence once a sync has occurred.
{% endhint %}

### Status Sync

| Control                          | Description                                                                                                                                                                                                                                                                                                                                                    |
| -------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Synchronize completed status** | When enabled, marking a Jira ticket as Done or Closed automatically updates the corresponding Pharos issue to Completed status. This is the foundation of the [reoccurrence handling](https://docs.pharos.ai/configuration-guide/ticketing.md#reoccurrence-handling) — if a completed issue reoccurs, Pharos creates a new ticket and links it to the old one. |

***

## Recommended Settings

For most organizations starting with Jira integration:

| Control                                      | Recommended               | Why                                                             |
| -------------------------------------------- | ------------------------- | --------------------------------------------------------------- |
| **Synchronize related tickets and Issues**   | Enabled                   | Keeps Jira relationships in sync with Pharos                    |
| **Synchronize duplicate tickets and Issues** | Enabled                   | Prevents duplicate tickets from cluttering the backlog          |
| **Automatically update ticket priority**     | Enabled                   | Triage in Pharos → priority flows to Jira                       |
| **Automatically update Issue priority**      | Enabled                   | Priority changes in Jira reflect in Pharos                      |
| **Synchronize completed status**             | Enabled                   | Closing tickets in Jira completes issues in Pharos              |
| **Auto Generate Similarity Labels**          | Disabled initially        | Enable once you understand how labels affect your Jira workflow |
| **Auto Relate Tickets With Similar Errors**  | Disabled initially        | Enable after establishing log-level ticketing rules             |
| **Create Unique Tickets by Org**             | Disabled unless multi-org | Only needed with Connected Orgs                                 |

***

## Environment-Specific Defaults

Each org (production, sandbox) has its own defaults configuration. After a sandbox refresh:

* Review whether sync settings should match production or differ
* Consider disabling **Synchronize completed status** in sandbox if you don't want sandbox ticket closures affecting issue status
* Use the [Quick Start](https://docs.pharos.ai/configuration-guide/quick-start.md) wizard **Sandbox Refresh** option to reset integration state

***

## Related

* [Authentication](https://docs.pharos.ai/configuration-guide/integrations/jira/authentication.md) — Connect Pharos to Jira
* [Ticketing Actions](https://docs.pharos.ai/configuration-guide/ticketing/actions.md) — Template configuration (project, issue type, merge fields)
* [Ticketing Rules](https://docs.pharos.ai/configuration-guide/ticketing/rules.md) — Automated ticket creation criteria
* [Ticketing Overview](https://docs.pharos.ai/configuration-guide/ticketing.md) — Manual creation, sync behavior, best practices

{% hint style="success" %}
**Next Step:** Create [Ticketing Actions](https://docs.pharos.ai/configuration-guide/ticketing/actions.md) to define your ticket templates, then set up [Ticketing Rules](https://docs.pharos.ai/configuration-guide/ticketing/rules.md) to automate ticket creation.
{% endhint %}
