> For the complete documentation index, see [llms.txt](https://docs.drizz.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.drizz.dev/automate-and-integrate/jira.md).

# Jira

Drizz creates a Jira issue from a failed test.

|                    |                                                                                            |
| ------------------ | ------------------------------------------------------------------------------------------ |
| **What it does**   | Creates a Jira issue when a test fails                                                     |
| **Authentication** | A single shared token for the whole organization                                           |
| **You can set**    | The assignee                                                                               |
| **You can't set**  | The reporter                                                                               |
| **Watch out**      | Every ticket is reported by whoever connected the integration, not by whoever ran the test |

## Prerequisites

* Drizz organization account
* A Jira project to file issues into
* A Jira account whose token authenticates the integration — a service account, not a personal account
* Setup details from your Drizz contact

## Attribution

The integration authenticates with **one shared token**. Every issue is attributed to the account that connected the integration, regardless of who triggered the run.

| Field    | Configurable | Value on a generated ticket                |
| -------- | ------------ | ------------------------------------------ |
| Assignee | Yes          | Whoever you configure                      |
| Reporter | No           | The account that connected the integration |

Consequences:

| Constraint                                        | What to do                                                                               |
| ------------------------------------------------- | ---------------------------------------------------------------------------------------- |
| The reporter is identical on every ticket         | Do not key filters, dashboards or automation on it                                       |
| Run context is not carried into any Jira field    | Put the triggering user, the test plan and the report link in the summary or description |
| A personal account becomes the permanent reporter | Connect with a service account                                                           |

## Common mistakes

| What you did                                      | What happens                                              |
| ------------------------------------------------- | --------------------------------------------------------- |
| Filtered Jira by reporter to find your failures   | Every Drizz ticket has the same reporter                  |
| Connected the integration with a personal account | Every generated ticket is attributed to you, indefinitely |
| Expected the triggering user's name on the ticket | It isn't carried through. Put it in the description       |
| Assumed one ticket per unique failure             | Deduplication behavior isn't confirmed                    |

## Next

* [When a step fails](/reports-and-debugging/when-a-step-fails.md) — triaging before you file
* [Statuses](/reports-and-debugging/statuses.md) — what counts as a failure
* [CI/CD](/automate-and-integrate/ci-cd.md) — triggering runs from a pipeline

***

*Last updated: 6 August 2026*