Skip to main content
Back to Search AI connectors list Jira is a project management and issue-tracking platform that enables teams to plan, track, and coordinate tasks through customizable workflows. The Jira connector lets Search AI ingest, index, and search through issues, dashboards, and filters, improving accessibility to content from Jira Cloud.

​
Connector Specifications

​
Prerequisites

An Atlassian account with admin access. This account fetches content and resolves access permissions for indexed content.

​
Connector Configuration

​
Create an API Token in Atlassian

Search AI interacts with Jira through APIs. Create an API token in your Atlassian account following the Atlassian documentation. Enable the following scopes when generating the API token:
  • read:application-role:jira
  • read:comment:jira
  • read:comment.property:jira
  • read:dashboard:jira
  • read:filter:jira
  • read:group:jira
  • read:issue-details:jira
  • read:issue-type-hierarchy:jira
  • read:issue-type:jira
  • read:jira-work
  • read:jql:jira
  • read:project-category:jira
  • read:project-role:jira
  • read:project-version:jira
  • read:project.component:jira
  • read:project.property:jira
  • read:project:jira
  • read:user:jira

​
Configure the Jira Cloud Connector in Search AI

  1. Go to the Connectors page and select Jira Cloud.
  2. Create or select a Profile.
    Each profile saves its own credentials, filters, and mappings. You can maintain multiple profiles under a single connector.
  3. In the profile setup, provide the following fields:
  4. Click Connect to authenticate the profile.
  5. Repeat the process to add additional profiles as needed.

​
Multiple Authentication Profiles

A single Jira Cloud connector supports multiple authentication profiles.
  • Each profile uses its own credentials and domain.
  • Content sync runs across all configured profiles.
  • This simplifies multi-account management, reduces the need for multiple connectors, and scales better for enterprise use cases.

​
Content Ingestion

The connector ingests three object types from Jira. By default, content from the past 90 days is fetched.

​
Issues

​
Dashboards

​
Filters

All timestamps are stored in UTC. The doc_source_type field distinguishes content types. Issue comments are concatenated into a single field; individual comment metadata is not indexed.

​
Content Filtering

The Jira connector supports standard and advanced filters to control which content is ingested. Go to the Manage Content page and select the Object Type to define which content types to ingest. All filter settings apply only to the selected object type. Manage Content Select Ingest filtered content and click Edit Configuration to apply filters. Filters

​
Standard Filters

Use standard filters to ingest content from specific projects. Select one or more projects - all items of the selected object type within those projects are ingested. You can also set a Started On date to control how far back content is synced. This field defines the earliest date from which Jira content is eligible for sync - both for the initial sync and all subsequent incremental syncs. The Started On field is optional; if left blank, no date boundary is applied and all available Jira content is eligible for sync.

​
Advanced Filters

Advanced filters provide granular control through field-based rules. For example, ingest only specific issue types from a particular project. Advanced Filters Choose from commonly used fields in the dropdown or enter any valid Jira field name. The field name must match the field name for the selected object in your Jira instance.

​
Filter Precedence and Scope

  • Advanced filters override standard filters when their criteria conflict. For example, if a standard filter selects Project A and an advanced filter specifies Project B by key, Project B takes precedence.
  • Filters apply only to the selected object type. An advanced filter set for issues is ignored if only dashboards are selected on the Manage Content page.

​
Access Control

​
Issues

  • Each issue is linked to a project via a unique Project ID.
  • The Project ID is stored in the RACL field of the ingested chunks.
  • Search AI automatically resolves permission entities for Jira issues — it identifies users with access to each project and associates them with the corresponding Project ID. Manual Permission Entity mapping is not required.

​
Dashboards and Filters

When Jira dashboards or filters are shared, Search AI populates the RACL field to mirror those sharing settings: If multiple sharing options apply, all corresponding IDs and emails are included in the RACL field. Search AI automatically resolves permission entities — manual mapping through Permission Entity APIs is not required.