> ## 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.

# Integrations Overview

> Set up integrations and browse all available integrations.

## Setting up your integrations

![Integrationsoverview 1](https://mintcdn.com/spur/ZA7H1zBduwx6X_7a/images/analysing-tests/integrations/overview/integrations-overview.gif?s=58f4f4d43725509cadc9060779e71b04)

Find your integrations here. Connect them through this page.

1. Click the User Profile button in the top right, from any page.
2. Click Integrations in the dropdown.
3. Connect and manage your integrations.

After you authorize Slack, Linear, or Jira, Spur returns you to the Integrations page and shows whether the connection succeeded, failed, or was canceled. If it failed, click **Connect** to try again.

## Reconnect required

Spur checks each connection with the provider when you open the Integrations page. If Slack, Linear, Jira, Azure DevOps, or Vercel rejects Spur's token, for example because it was revoked or expired, the card shows a **Reconnect required** badge and the reason below it.

Click **Reconnect** on the card to run the same connect flow again. Your existing settings are kept.

## Available integrations

### Issue tracking & bug reporting

> [!NOTE]
>
> Jira and Linear follow the same workflow in Spur. Both let you create bug tickets from test failures with auto-populated details. The setup and ticket creation steps are identical across both integrations.
>
> Azure DevOps files the same auto-populated content, but it connects with a personal access token instead of an OAuth authorization, and anyone with access to the Application can set it up. Follow the [Azure DevOps guide](https://docs.spurtest.com/analysing-tests/integrations/azure-devops.md) rather than the steps above.
>
> ClickUp connects with OAuth. See [ClickUp Tasks](https://docs.spurtest.com/analysing-tests/integrations/clickup.md) for workspace and list setup.
>
> Asana also connects with an OAuth authorization. If your authorization covers more than one workspace, you pick one after you connect. See the [Asana guide](https://docs.spurtest.com/analysing-tests/integrations/asana.md) for workspace and project setup.

> [card] [Jira](https://docs.spurtest.com/analysing-tests/integrations/jira.md)
>
> Create detailed Jira tickets directly from test failures with screenshots, logs, and reproduction steps.

> [card] [Linear](https://docs.spurtest.com/analysing-tests/integrations/linear.md)
>
> Create Linear issues directly from test failures with auto-populated details and reproduction steps.

> [card] [Azure DevOps](https://docs.spurtest.com/analysing-tests/integrations/azure-devops.md)
>
> Create Azure DevOps work items from test results, with project and field defaults from your connected Application.

> [card] [Asana](https://docs.spurtest.com/analysing-tests/integrations/asana.md)
>
> Create Asana tasks from test results. Spur AI and the PR Agent can read linked tasks.

> [card] [ClickUp](https://docs.spurtest.com/analysing-tests/integrations/clickup.md)
>
> Create ClickUp tasks from test results. Spur AI and the PR Agent can read linked tasks.

### Communication & notifications

> [card] [Slack](https://docs.spurtest.com/analysing-tests/integrations/slack.md)
>
> Real-time notifications and alerts in your Slack workspace

> [card] [Email](https://docs.spurtest.com/analysing-tests/integrations/email.md)
>
> Customizable email notifications and reports

### Development workflows

> [!NOTE]
>
> GitHub Actions and GitLab CI/CD run configured Test Plans from your pipeline. GitHub also supports the [PR Agent](https://docs.spurtest.com/running-tests/cicd/pr-agent.md), which selects relevant saved tests and generates browser tests for pull request changes.

> [card] [GitHub](https://docs.spurtest.com/analysing-tests/integrations/github.md)
>
> Choose the PR Agent to test code changes or GitHub Actions to run configured Test Plans.

> [card] [GitLab](https://docs.spurtest.com/analysing-tests/integrations/gitlab.md)
>
> Run Spur tests in your GitLab CI/CD pipelines with automated test execution on merge requests.


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