The Jira source indexes issues from one or more projects — summary, description, status, labels, and the full comment thread — via the Jira Cloud REST API. It’s the answer to “didn’t we hit this before?”: the reasoning behind a fix usually lives in an issue’s comments and nowhere else, so indexing them turns a ticket archive into something the assistant can actually use.
This is Jira software/work projects. For Jira Service Management — customer-facing requests, ticket deflection, and agent copilot drafts — see Jira Service Management.

​
What gets indexed

Each issue becomes one document containing:
  • Summary and description
  • Current status and labels
  • Every comment, in order
Issues are fetched newest-first across the projects you name.

​
Connect

1

Create an API token

At id.atlassian.com, create an API token. Note the account email it belongs to — you need both.The token inherits that account’s permissions, so it sees exactly the projects that user can see. Use a dedicated service account if you want to control that precisely.
2

Add the source

In Knowledge Base → Sources, add a Jira source:
3

Sync

The first sync starts automatically. Watch progress under the source’s page, and check what landed under Documents.

​
Keeping it fresh

Jira re-syncs every 10 minutes — no configuration, and no manual sync button, since waiting for the next run is never slower. See Sources Overview.

​
Keeping issues off your public widget

Internal issue trackers usually shouldn’t answer questions on a public docs site. Two options:
  • Set default_visibility to restricted in the source config, so every document it creates is withheld from the widget, SDKs, and public API while remaining available to your team and the bots.
  • Put it in a knowledge base whose type is internal, which has no public surface at all — see Knowledge Bases.
default_visibility applies to documents as they are created. Changing it later leaves already-indexed documents alone — use the source’s bulk re-label to catch them up.

​
Scoping which issues answer

Group this source with related ones so retrieval can be scoped per surface — engineering issues for the internal assistant, docs only for the public widget. See Source Groups.