> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.airweave.ai/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.airweave.ai/_mcp/server.

# Jira

> Jira integration with Airweave

{/* AUTO-GENERATED CONTENT START */}

<img src="https://fdr-prod-docs-files-public.s3.us-east-1.amazonaws.com/airweave.docs.buildwithfern.com/2026-05-20T11%3A36%3A51.367Z/docs/pages/connectors/jira/icon.svg?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=AKIA6KXJSKKNFOCF7G4B%2F20260807%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260807T163122Z&X-Amz-Expires=604800&X-Amz-Signature=cab7274b24745101cf563d13408f69f83aaef3279f746cbc714dedeec4c1a7bc&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject" alt="Jira logo" width="48" height="48" />

<h1>
  Jira
</h1>

This connector enables AI agents and RAG systems to retrieve context from Jira through Airweave's unified search layer.

## Configuration

Jira source connector integrates with the Jira REST API to extract project management data.

Connects to your Jira Cloud instance. Optionally integrates with Zephyr Scale
for test management entities (test cases, test cycles, test plans) when a
Zephyr Scale API token is provided.

It provides comprehensive access to projects, issues, and their
relationships for agile development and issue tracking workflows.

#### [View Source Code](https://github.com/airweave-ai/airweave/tree/main/backend/airweave/platform/sources/jira.py)

Explore the Jira connector implementation

### Authentication

This connector uses **OAuth 2.0 authentication**. You can connect through the Airweave UI or API using the OAuth flow.

**Supported authentication methods:**

* OAuth Browser Flow (recommended for UI)
* OAuth Token (for programmatic access)
* Auth Provider (enterprise SSO)

### Configuration Options

This connector does not have any additional configuration options.

## Data Models

The following data models are available for this connector:

#### JiraProjectEntity

Schema for a Jira Project.

Reference:
[https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-projects/](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-projects/)

| Field           | Type           | Description                                |
| --------------- | -------------- | ------------------------------------------ |
| project\_id     | str            | Unique numeric identifier for the project. |
| project\_name   | str            | Display name of the project.               |
| project\_key    | str            | Unique key of the project (e.g., 'PROJ').  |
| description     | Optional\[str] | Description of the project.                |
| web\_url\_value | Optional\[str] | Link to the project in Jira.               |

#### JiraIssueEntity

Schema for a Jira Issue.

Reference:
[https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/)

| Field           | Type           | Description                                 |
| --------------- | -------------- | ------------------------------------------- |
| issue\_id       | str            | Unique identifier for the issue.            |
| issue\_key      | str            | Jira key for the issue (e.g. 'PROJ-123').   |
| summary         | str            | Short summary field of the issue.           |
| description     | Optional\[str] | Detailed description of the issue.          |
| status          | Optional\[str] | Current workflow status of the issue.       |
| issue\_type     | Optional\[str] | Type of the issue (bug, task, story, etc.). |
| project\_key    | str            | Key of the project that owns this issue.    |
| created\_time   | datetime       | Timestamp when the issue was created.       |
| updated\_time   | datetime       | Timestamp when the issue was last updated.  |
| web\_url\_value | Optional\[str] | Link to the issue in Jira.                  |

#### ZephyrTestCaseEntity

Schema for a Zephyr Scale Test Case.

Test cases have keys in the format PROJECT-T### (e.g., PROJ-T1, PROJ-T2).

Reference:
[https://support.smartbear.com/zephyr-scale-cloud/api-docs/#tag/Test-Cases](https://support.smartbear.com/zephyr-scale-cloud/api-docs/#tag/Test-Cases)

| Field           | Type           | Description                                              |
| --------------- | -------------- | -------------------------------------------------------- |
| test\_case\_id  | str            | Unique internal identifier for the test case.            |
| test\_case\_key | str            | Zephyr Scale key for the test case (e.g., 'PROJ-T1').    |
| name            | str            | Name/title of the test case.                             |
| objective       | Optional\[str] | Objective or purpose of the test case.                   |
| precondition    | Optional\[str] | Preconditions required before executing the test.        |
| status\_name    | Optional\[str] | Current status of the test case (e.g., Draft, Approved). |
| priority\_name  | Optional\[str] | Priority level of the test case.                         |
| folder\_path    | Optional\[str] | Folder path where the test case is organized.            |
| project\_key    | str            | Key of the Jira project this test case belongs to.       |
| created\_time   | datetime       | Timestamp when the test case was created.                |
| updated\_time   | datetime       | Timestamp when the test case was last updated.           |
| web\_url\_value | Optional\[str] | Link to the test case in Zephyr Scale.                   |

#### ZephyrTestCycleEntity

Schema for a Zephyr Scale Test Cycle.

Test cycles have keys in the format PROJECT-R### (e.g., PROJ-R1, PROJ-R2).
They represent a collection of test executions for a specific testing iteration.

Reference:
[https://support.smartbear.com/zephyr-scale-cloud/api-docs/#tag/Test-Cycles](https://support.smartbear.com/zephyr-scale-cloud/api-docs/#tag/Test-Cycles)

| Field            | Type           | Description                                                               |
| ---------------- | -------------- | ------------------------------------------------------------------------- |
| test\_cycle\_id  | str            | Unique internal identifier for the test cycle.                            |
| test\_cycle\_key | str            | Zephyr Scale key for the test cycle (e.g., 'PROJ-R1').                    |
| name             | str            | Name/title of the test cycle.                                             |
| description      | Optional\[str] | Description of the test cycle.                                            |
| status\_name     | Optional\[str] | Current status of the test cycle (e.g., Not Executed, In Progress, Done). |
| folder\_path     | Optional\[str] | Folder path where the test cycle is organized.                            |
| project\_key     | str            | Key of the Jira project this test cycle belongs to.                       |
| created\_time    | datetime       | Timestamp when the test cycle was created.                                |
| updated\_time    | datetime       | Timestamp when the test cycle was last updated.                           |
| web\_url\_value  | Optional\[str] | Link to the test cycle in Zephyr Scale.                                   |

#### ZephyrTestPlanEntity

Schema for a Zephyr Scale Test Plan.

Test plans have keys in the format PROJECT-P### (e.g., PROJ-P1, PROJ-P2).
They represent a high-level collection of test cycles for release planning.

Reference:
[https://support.smartbear.com/zephyr-scale-cloud/api-docs/#tag/Test-Plans](https://support.smartbear.com/zephyr-scale-cloud/api-docs/#tag/Test-Plans)

| Field           | Type           | Description                                                        |
| --------------- | -------------- | ------------------------------------------------------------------ |
| test\_plan\_id  | str            | Unique internal identifier for the test plan.                      |
| test\_plan\_key | str            | Zephyr Scale key for the test plan (e.g., 'PROJ-P1').              |
| name            | str            | Name/title of the test plan.                                       |
| objective       | Optional\[str] | Objective or purpose of the test plan.                             |
| status\_name    | Optional\[str] | Current status of the test plan (e.g., Draft, Approved, Archived). |
| folder\_path    | Optional\[str] | Folder path where the test plan is organized.                      |
| project\_key    | str            | Key of the Jira project this test plan belongs to.                 |
| created\_time   | datetime       | Timestamp when the test plan was created.                          |
| updated\_time   | datetime       | Timestamp when the test plan was last updated.                     |
| web\_url\_value | Optional\[str] | Link to the test plan in Zephyr Scale.                             |

{/* AUTO-GENERATED CONTENT END */}