> ## Documentation Index
> Fetch the complete documentation index at: https://koreai.mintlify.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Jira On-Premise Connector

<Badge icon="arrow-left" color="gray">[Back to Search AI connectors list](/ai-for-service/searchai/content-sources#supported-connectors)</Badge>

Jira is a project management and issue-tracking platform that enables teams to plan, track, and coordinate tasks through customizable workflows.

The Jira On-Premise connector lets Search AI ingest, index, and search through **Work Items** from a self-hosted Jira server, improving accessibility to content from on-premise Jira deployments.

## Connector Specifications

| Specification                   | Details    |
| ------------------------------- | ---------- |
| Repository type                 | On-Prem    |
| Supported content               | Work Items |
| RACL support                    | Yes        |
| Content filtering               | Yes        |
| Automatic permission resolution | Yes        |

## Prerequisites

An Atlassian account with admin access. This account fetches content and resolves access permissions for indexed content. Search AI uses basic authentication to communicate with the Jira server.

### Configure the Jira Cloud Connector in Search AI

1. Go to the **Connectors** page and select **Jira Server Connector**.

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:

   | Field         | Description                                                   |
   | ------------- | ------------------------------------------------------------- |
   | **Name**      | Unique name for the connector profile                         |
   | **Email**     | Atlassian account email address used for indexing             |
   | **Domain**    | Jira Cloud domain (For example `<your-domain>.atlassian.net`) |
   | **API Token** | API token generated from your Atlassian account               |

4. Click **Connect** to authenticate the profile.

5. Repeat the process to add additional profiles as needed.

### Multiple Authentication Profiles

A single Jira Server 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 **Work Items** from Jira. Each work item is indexed with the following fields:

| Field                 | Description                                          |
| --------------------- | ---------------------------------------------------- |
| `title`               | Summary or title of the work item                    |
| `content`             | Full description of the work item                    |
| `url`                 | Direct link to the work item in Jira                 |
| `doc_created_by_name` | Name of the user who created the work item           |
| `doc_created_on`      | Timestamp when the work item was created (UTC)       |
| `doc_updated_on`      | Timestamp of the latest update (UTC)                 |
| `doc_source_type`     | Type of content ingested                             |
| `priority`            | Work item priority (High, Medium, Low, etc.)         |
| `status`              | Work item status (open, closed, etc.)                |
| `assignee`            | Username of the currently assigned person            |
| `reporter_name`       | Name of the user who reported the work item          |
| `comments`            | All comments concatenated, including commenter names |
| `issueType`           | Type of work item (Bug, Task, Story)                 |
| `resource_type`       | Type of work item                                    |
| `project_name`        | Name of the Jira project                             |

<Note>All timestamps are stored in UTC. Work item comments are concatenated into a single field; individual comment metadata is not indexed.</Note>

## Content Filtering

The Jira Server connector supports standard and advanced filters to control which content is ingested.

On the **Manage Content** page, select **Ingest All Content** to ingest everything, or select **Ingest Filtered Content** and click **Configure** for selective ingestion.

<img src="https://mintcdn.com/koreai/srjnuPslD4wwfWXb/ai-for-service/searchai/connectors/images/jiraonprem/standard-filter.png?fit=max&auto=format&n=srjnuPslD4wwfWXb&q=85&s=badbc0a9c908c916c3eacb4e9fd80081" alt="Standard Filters" width="1424" height="850" data-path="ai-for-service/searchai/connectors/images/jiraonprem/standard-filter.png" />

### Standard Filters

Use standard filters to ingest work items from specific projects. Select one or more projects — all work items within those projects are ingested. You can also define a **date range** using the calendar selector to limit ingestion to a specific time frame.

### Advanced Filters

Advanced filters provide granular control through **field-based rules**. Since only Work Items are supported for the Jira server connector, rules apply to work items only. For example, ingest only specific types of work items from a particular project.

<img src="https://mintcdn.com/koreai/srjnuPslD4wwfWXb/ai-for-service/searchai/connectors/images/jiraonprem/advanced-filters.png?fit=max&auto=format&n=srjnuPslD4wwfWXb&q=85&s=528c889de2a7d68b52ce0742e0fb25a0" alt="Advanced Filters" width="1420" height="839" data-path="ai-for-service/searchai/connectors/images/jiraonprem/advanced-filters.png" />

Select Work Items fields from the parameter list, then provide operators and values to set filter conditions. Add custom fields as needed — field names must match the field names in your Jira server instance.

### Filter Precedence

**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.

## Access Control

### Work Items

* Each work item is linked to a project via a unique **Project ID**.
* This Project ID is stored in the **RACL field** of the ingested chunks.
* Associate users with a Project ID using the **Permission Entity APIs**. Users added to the corresponding permission entities gain access to work items associated with those projects.