Skip to main content
The Jira connector indexes issues from your Jira projects, including descriptions, comments, and metadata. Engineering requirements buried in epics, bug context in comment threads, and sprint decisions across projects become searchable through Hadiq.io.

​
What gets indexed

  • Issues: title, description, and all comments
  • Epics: indexed as both a searchable document and a hierarchy node (issues within the epic are grouped under it)
  • Metadata: status, priority, assignee, reporter, labels, issue type, project, parent, created/updated dates
  • All issue types: stories, tasks, bugs, epics, subtasks, and custom types
Issues with labels you configure to skip are excluded from indexing. Issues exceeding the configured size limit are also skipped.

​
Prerequisites

You need credentials for a Jira account with read access to the projects you want to index.
  • Jira Cloud: use your Atlassian account email and an API token from id.atlassian.com.
  • Jira Data Center / Server: use your username and a personal access token generated in your Jira profile settings.

​
Connect Jira

1

Go to Admin > Connectors

Navigate to Admin Panel > Connectors and select Jira.
2

Enter your Jira base URL

Enter the base URL of your Jira instance. For Jira Cloud, this is https://yourcompany.atlassian.net. For Data Center or Server, use your self-hosted URL.
3

Add credentials

Jira Cloud:
  • Email: your Atlassian account email
  • API token: the token generated at id.atlassian.com
Jira Data Center / Server:
  • Username: your Jira username
  • Personal access token: the token from your Jira profile
4

Configure scope (optional)

Leave the scope fields empty to index all issues the account can access.To limit indexing to a specific project, enter the project key (e.g., ENG, PROJ).For precise control, enter a custom JQL query:
The connector automatically appends time-range filters to your JQL during incremental syncs.
5

Save

Click Save. Hadiq.io connects to Jira and begins indexing. Large projects with many issues and comments may take a while on the initial sync.
If your Jira Data Center instance is behind a firewall or VPN, Hadiq.io must be deployed in a network that can reach it. Hadiq.io Cloud cannot reach privately hosted Jira instances.

​
Permission syncing

Hadiq.io reads project-level permissions from Jira and enforces them in search results. Users only see issues from projects they have access to in Jira. Permissions are determined at the project level — if a user has access to a Jira project, they can see all issues in that project through Hadiq.io.
Automatic permission sync — where Hadiq.io continuously re-checks Jira project access — is available on the Enterprise plan.

​
Limitations

  • Jira attachments (uploaded files) are not indexed by default.
  • Custom fields with complex formats may not be fully extracted as text.
  • Issues exceeding the size limit (default 100KB of text content) are skipped to prevent indexing failures on very large tickets.
  • Comments from specific email addresses can be excluded from indexed content via connector configuration.