Compatible with Fusion version: 4.0.0 through 5.12.0
The Jira V1 connector retrieves data from an instance of Atlassian’s Jira issue tracking system.
ImportantV1 deprecation and removal noticeStarting in Fusion 5.12.0, all V1 connectors are deprecated. This means they are no longer being actively developed and will be removed in Fusion 5.13.0.The replacement for this connector is using the Jira recipe with the REST V2 connector.If you are using this connector, you must migrate to the replacement connector or a supported alternative before upgrading to Fusion 5.13.0. We recommend migrating to the replacement connector as soon as possible to avoid any disruption to your workflows.
Connector flow The Jira connector uses the Jira REST API to retrieve the following Jira elements:
  • Projects
  • Issues
  • Comments
  • Worklogs
  • Attachments
Jira access to projects and issues may be restricted to certain users. Access of restricted information requires a Jira username and password. The Jira V1 connector first requests a list of all projects, and for each project, it finds all issues. For each issue, information on summary, priority, assignee, and more is retrieved. Worklogs, comments, and attachments are treated as new entries (issue links) and indexed as a new document, not as a component of the issue itself.

​
Prerequisites

Perform these prerequisites to ensure the connector can reliably access, crawl, and index your data. Proper setup helps avoid configuration or permission errors, so use the following guidelines to keep your content available for discovery and search in Fusion.

​
Configure access in Jira

  • Have Jira Cloud or Jira Server/Data Center with REST API access.
  • Create or use a user account with API access and permission to read issues, projects, and comments.
  • If you are crawling attachments, the user account needs permission to view attachments.
  • If you are using security trimming, the user account needs permission to browse users/groups.

​
Confirm network connectivity

  • Fusion must be able to reach your Jira instance over HTTPS.
    • For Jira Cloud, allow outbound traffic to \https://DOMAIN_NAME.atlassian.net.
    • For Jira Server, ensure firewall rules allow Fusion access to the Jira REST endpoints.

​
Security trimming access

  • If you are using security trimming for document-level security, additional REST API access is needed.
    • The user account must have access to Jira’s Users and Groups APIs.

​
Authentication

Setting up the correct authentication according to your organization’s data governance policies helps keep sensitive data secure while allowing authorized indexing. The authentication options for the Jira V1 connector in Lucidworks Fusion depend on whether you’re using Jira Cloud or Jira Server/Data Center. The two methods of authenticating are basic authentication and token authentication. Jira Cloud does not support password-based login, so you must use an API token. Go to Atlassian API tokens to generate a new token. For Jira Server/Data Center, you can use a username and password, unless it’s disabled by your organization’s policies. Here are the steps to authenticate:
  1. In Fusion, use your email address as the Jira username and the password or token as Jira Password or API Token.
  2. Save and test the connection. Fusion should return “Success” or a detailed error such as 401, invalid token.

​
Configuration

When entering configuration values in the UI, use unescaped characters, such as \t for the tab character. When entering configuration values in the API, use escaped characters, such as \\t for the tab character.