Skip to main content

Jira Integration

Jira integration allows you to sync issues from your Jira Cloud projects into your vector store. Each issue is imported as a separate document, including its summary, description, metadata, and comments.

Prerequisites​

Before connecting Jira, ensure you have:

  1. A Jira Cloud account (e.g., yoursite.atlassian.net)
  2. Access to the projects you want to sync
Jira Cloud Only

This connector works with Jira Cloud only. Jira Server and Jira Data Center are not supported.

Connecting Jira​

  1. Navigate to Sources in Vector Data Loader
  2. Click the Jira card in "Add a Source"
  3. Review the requested permissions and click Connect
  4. You'll be redirected to Atlassian's consent screen
  5. Grant the requested permissions (read-only access to Jira issues and users)
  6. After authorization, you'll be redirected back with Jira connected
Separate from Confluence

Even though both Jira and Confluence use Atlassian OAuth, they require separate connections. Connecting Confluence does not give access to Jira, and vice versa.

Browsing Jira Content​

Once connected, click Browse on your Jira source to explore your content:

Projects View (Root Level)​

At the root level, all accessible Jira projects are listed. Each project appears as a folder you can click into.

Issues View (Inside a Project)​

Click a project to see its issues, sorted by most recently updated. Each issue shows:

  • Issue summary (title)
  • Last updated timestamp
  • Issue type (e.g., Story, Bug, Task)
  • Status badge (e.g., To Do, In Progress, Done)
  • Priority (e.g., High, Medium, Low)
  • Comment count (number of comments on the issue)

This metadata helps you identify the right issues to sync without needing to open each one in Jira.

Select individual issues using the checkboxes, then click Sync Selected to import them.

The Jira browser includes a JQL search bar that lets you find issues across all your accessible projects using Jira Query Language (JQL) — Jira's built-in search syntax.

  1. Open the Jira browser by clicking Browse on your Jira source
  2. Type a JQL query in the search bar at the top of the dialog
  3. Press Enter or click the search icon to execute the query
  4. Browse the matching issues and select the ones you want to sync
  5. Click the X button to clear the search and return to project browsing
JQL searches across all projects

Unlike browsing into a single project, JQL search returns matching issues from all accessible projects. This is useful when you want to sync issues across multiple projects at once.

Common JQL Examples​

QueryDescription
status = "In Progress"Find all in-progress issues
project = "PROJ" AND priority = HighHigh-priority issues in a specific project
assignee = currentUser()Issues assigned to you
labels = "frontend" ORDER BY updated DESCLabeled issues, newest first
type = Bug AND status != DoneOpen bugs across all projects
updated >= -7dIssues updated in the last 7 days
Learn more about JQL

For advanced queries, see Atlassian's JQL documentation.

What Gets Synced​

When you sync a Jira issue, the following content is extracted:

ContentSynced
Issue summary (title)✅
Description (full text)✅
Status✅
Priority✅
Issue type✅
Labels✅
Assignee✅
Reporter✅
Comments (all, with authors and dates)✅
Created and updated timestamps✅
Attachments❌ (text content only)
Custom fields❌

Content Structure​

Each synced issue is formatted as a structured document with numbered comments for better readability:

# Issue Summary

**Key:** PROJ-123
**Type:** Story
**Status:** In Progress
**Priority:** High
**Labels:** frontend, urgent
**Assignee:** Jane Smith
**Reporter:** John Doe
**Created:** 2026-01-15T10:00:00Z
**Updated:** 2026-02-20T14:30:00Z

## Description

[Full issue description text]

## Comments

### Comment 1 of 3
**Jane Smith** (2026-02-18T09:00:00Z):
[Comment text]

---

### Comment 2 of 3
**John Doe** (2026-02-19T11:30:00Z):
[Comment text]

---

### Comment 3 of 3
**Jane Smith** (2026-02-20T14:30:00Z):
[Comment text]

Comments are numbered sequentially (e.g., "Comment 1 of 3") and separated by horizontal rules, making it easy to navigate through lengthy issue discussions. The comment count is also visible in the browse view before syncing.

Re-sync Behavior​

When re-syncing an issue:

  • A content hash is generated from the extracted text
  • If the hash matches the previous sync, the issue is treated as unchanged (lower credit cost)
  • If the content has changed (description edited, new comments, status change), a full re-sync is performed

Credit Cost​

OperationCredits
Sync issue (new or changed)20 (standard) or 40 (enhanced)
Re-sync unchanged issue5

Troubleshooting​

Token expired or "Unauthorized" error​

Your OAuth token may have expired. Click Reconnect on the Jira source card to re-authorize through Atlassian.

Can't see projects​

  • Verify you have access to the projects in Jira
  • The connector only shows projects your Jira account can access
  • Check that your Jira Cloud site is active

No issues appearing in a project​

  • Ensure the project has issues (empty projects show no results)
  • The connector lists up to 50 issues per project, sorted by most recently updated

"Jira API error" messages​

  • Confirm your Jira Cloud site is accessible
  • Try disconnecting and reconnecting the source
  • If the error persists, the Jira API may be temporarily unavailable

Security Considerations​

  • The connector requests read-only permissions (read:jira-work, read:jira-user)
  • OAuth tokens are encrypted before storage in the database
  • The app never creates, modifies, or deletes your Jira data
  • Token refresh is handled automatically when tokens expire