---
sidebar_position: 2
title: Jira Integration
---

# Jira Integration

Connect your Jira workspace to sync tickets into Zibby for analysis and test generation.

## How It Works

Zibby uses OAuth 2.0 to connect to your Atlassian/Jira account. Once connected, it syncs tickets from your selected Jira project and keeps them up to date.

## Connect Jira

1. Go to your project's **Settings** page in the Zibby dashboard
2. Under **Integrations**, click **Connect Jira**
3. You'll be redirected to Atlassian to authorize Zibby
4. Grant access to your Jira workspace
5. You'll be redirected back to Zibby

## Select a Jira Space

After connecting:

1. Go to **Settings > Jira Configuration**
2. Select the Jira project/space to sync (e.g., "SCRUM", "ENG")
3. Zibby will import all tickets from that space

## Synced Data

For each ticket, Zibby imports:

- **Summary** and **Description** (including Atlassian Document Format)
- **Issue type** (Story, Bug, Task, etc.)
- **Priority** (High, Medium, Low)
- **Labels** and **Components**
- **Acceptance criteria** (from description)

## Ticket Management

In the **Tickets** page:

- Tickets sync automatically when you visit the page
- Drag and drop to reorder tickets by priority
- Click a ticket to view full details and run analysis
- Ticket order is preserved across sessions

## Reconnecting

Jira tokens expire periodically. If you see a "Please reconnect Jira" message:

1. Go to **Settings > Integrations**
2. Click **Reconnect** next to Jira
3. Re-authorize through the Atlassian OAuth flow

Your existing tickets and their order are preserved after reconnecting.

## Troubleshooting

**"Token refresh failed" error**

Your Jira refresh token has expired. Go to Settings and reconnect Jira. This won't affect your existing ticket data or analysis results.

**Tickets not syncing**

Make sure the correct Jira space is selected in Settings. Only tickets from the selected space are displayed.

**Duplicate tickets after reconnecting**

This shouldn't happen — Zibby matches tickets by their Jira key (e.g., SCRUM-123) and updates existing records rather than creating duplicates.