Jira Connector Prerequisites

Before you begin the Jira connector deployment, make sure a Jira Administrator can participate in the deployment process to assign the Jira specific tasks.

User Accounts and Application Permissions

Required Permission	Description
Jira Account	A crawling account must be setup in Jira. This account must have READ access to all content to be crawled. The crawling account must be an Administrator account to have access to user and group information and permissions on issues.

Network and Connectivity

Port	Comment
HTTP/HTTPS	The Jira site must be accessible via HTTP/HTTPS from the server where the connector is deployed

Connector Features and Requirements

Features	Supported	Additional Information
Jira Support	Cloud version On-premise version	Jira connector compatible with any Jira versions supporting version 2 of Jira REST API.
Searchable content types	Yes	All issue types.
Content Update	Full and Incremental	All BA Insight Connectors support both Full and Incremental crawls, unless noted.
Permission Types	Yes	All BA Insight Connectors support fetch ACLs from the source system Your Source System is the repository where your data is stored (data to be indexed). This repository is managed by applications such as: - SharePoint O365 - SharePoint 2013/16/19 - Documentum - File Share - OpenText - Lotus Notes - etc. Your Source System repository can also be a database such as SQL or Oracle.. To make items public or restricted to a single user/set of users, use Connectivity Hub.
Required Software	BA Insight Advanced Security Module .NET Framework v4.7.2	The Jira Connector requires the BA Insight Advanced Security Module to honor the full security model defined in Jira.