> ## Documentation Index
> Fetch the complete documentation index at: https://docs.spurtest.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Spur is an AI-powered QA engineer that lets teams create and run automated end-to-end tests for web and mobile apps using natural language.
> When answering questions about Spur, cite the relevant page from docs.spurtest.com.

# Jira Tickets

> Connect Spur with Jira to file bug tickets from failed test runs, sync ticket status back to Spur, and set project, priority, and assignee defaults.

## Setup

If you have not integrated Spur with Jira, follow the setup process [here](/analysing-tests/integrations/integrations).

## Overview

Connecting to our Jira integration allows you to create bug tickets directly from test failures. You can choose which project to send tickets to, along with details such as priority and assignee.

## Permissions

When you authorize the integration, Spur requests the following Jira OAuth scopes. Each one maps directly to a feature of the integration:

| Scope | Why Spur needs it |
| - | - |
| `read:jira-work` | Lists your projects, issue types, and issue fields so the ticket creation modal is pre-populated with your project's setup. Also used to fetch issue details for tickets linked to Spur tests. |
| `write:jira-work` | Creates bug tickets from test failures and attaches supporting evidence, such as test videos and screenshots, to the ticket. |
| `read:jira-user` | Fetches the names and avatars of assignable users so you can pick an assignee when creating a ticket. |
| `manage:jira-configuration` | Reads your Jira configuration — available priorities, statuses, and fields — so the ticket creation form matches your instance. Atlassian gates read access to these configuration objects behind this scope; Spur never creates or modifies projects, workflows, or custom fields. |
| `offline_access` | Keeps the integration connected by refreshing access tokens, so you don't have to re-authorize Spur. |

<Note>
  Spur only acts on your Jira workspace when you create a ticket from a test failure. It never modifies your Jira configuration or deletes data on its own.
</Note>

## Creating a ticket manually from a test failure

<Steps>
  <Step title="Review a test and initiate a bug report">
    After reviewing a test run, open the Share menu and click the "Create a Ticket" button to open the Jira ticket creation modal:

    <Frame caption="Bug report initiation showing the Share menu and the Create a Ticket options">
      <img src="https://mintcdn.com/spur/nNuvmyM4s84IFvTw/images/Integrations/share.png?fit=max&auto=format&n=nNuvmyM4s84IFvTw&q=85&s=0896982aaf8882f14eb4f6cab7efb787" width="300px" data-path="images/Integrations/share.png" />
    </Frame>
  </Step>

  <Step title="Jira ticket creation modal">
    The modal opens with pre-populated information from the test failure:

    <Frame caption="Jira ticket creation modal with auto-generated content">
      <img src="https://mintcdn.com/spur/nNuvmyM4s84IFvTw/images/Integrations/Jira/jira_full.png?fit=max&auto=format&n=nNuvmyM4s84IFvTw&q=85&s=0ce55247cc93ed2ed52561a07d504198" alt="" width="2366" height="1706" data-path="images/Integrations/Jira/jira_full.png" />
    </Frame>

    **Auto-Generated Fields:**

    * **Title**: Name of the Test
    * **Description**: Detailed bug report including:
      * Failure Reason
      * Reproduction steps
      * Test name and execution details
    * **Project**: The default project, if chosen in the Integrations page.
  </Step>

  <Step title="Customize ticket details">
    Edit the title and description, if necessary. Choose additional ticket details.

    <Frame caption="Customizing ticket details with additional information">
      <img src="https://mintcdn.com/spur/nNuvmyM4s84IFvTw/images/Integrations/Jira/jira_additional.png?fit=max&auto=format&n=nNuvmyM4s84IFvTw&q=85&s=cc19a833c9e3af2289c7f6ee93b6189c" width="300px" data-path="images/Integrations/Jira/jira_additional.png" />
    </Frame>

    **Customization Options:**

    * **Assignee**: Set who should handle the ticket
    * **Priority**: What is the urgency of this bug?
    * **Due Date**: When will this ticket be considered overdue?
  </Step>

  <Step title="Submit and track">
    Create the ticket!
  </Step>
</Steps>

## Viewing and syncing linked tickets

Once a Jira ticket is linked to a test, Spur displays it in the test's share panel with live status information pulled directly from Jira.

### Status pill

Each linked ticket shows a **status pill** reflecting its current Jira workflow state—for example, **Open**, **In Progress**, or **Done**. The status is displayed alongside the ticket key so you can see the current state at a glance without leaving Spur.

### Syncing ticket data

Click the **Sync** button next to a linked ticket to pull the latest information from Jira. Syncing updates:

* **Title** — Current ticket summary
* **Status** — Current workflow state
* **Assignee** — Current ticket owner
* **URL** — Link to the Jira issue

This is useful when a ticket has been updated in Jira since it was first linked—for example, if it has been reassigned, triaged, or resolved.

## Troubleshooting

### Common issues

**If fields are missing:**

* Your integration permissions may not be set properly. Try reintegrating from the Integrations page.

**Ticket Creation Failures:**

* Confirm you have chosen a proper project and issue type
* Check required field configurations

**Custom Required Fields:**

* If your Jira project has custom required fields, [contact the Spur team](/additional-resources/contact-us) for assistance with your integration setup.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.