> For the complete documentation index, see [llms.txt](https://mozarkdocs.gitbook.io/appx_documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mozarkdocs.gitbook.io/appx_documentation/test-context-manager-documentation/bug-tracking/creating-a-bug/jira-synchronization.md).

# JIRA synchronization

## JIRA synchronization

If JIRA integration is configured, bugs can synchronize between Test Manager and JIRA.

### What sync covers

Synchronization keeps linked bug records aligned between the two systems.

When a bug is created in Test Manager, a matching JIRA issue is created asynchronously.

The JIRA issue key appears on the bug page.

When a bug is updated in Test Manager, the linked JIRA issue is updated.

When a JIRA issue is updated, an inbound webhook can push changes back to Test Manager.

This requires webhook configuration in JIRA.

To trigger a manual sync:

1. Open the bug detail page.
2. Click **Re-Sync to JIRA**.

For integration setup, see the JIRA integration section.

<figure><img src="/files/p1NCQczE3pcGJRIo6sU0" alt=""><figcaption></figcaption></figure>

### Verify synchronization

Create or update a bug in Test Manager and confirm that the JIRA issue key appears.

Then update the linked JIRA issue and confirm the change returns to Test Manager when the webhook is configured.

If both directions work, synchronization is active.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://mozarkdocs.gitbook.io/appx_documentation/test-context-manager-documentation/bug-tracking/creating-a-bug/jira-synchronization.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.