The JIRA connector for Glean allows Glean to fetch and index content from JIRA, ensuring users can search and access documents with authorized permissions.

API Usage

Integration Features

The JIRA cloud connector has no specific version limitations, which is Atlassian’s SaaS offering of JIRA in the cloud. Glean supports the JIRA datacenter, a customer-managed deployment with a different connector and separate documentation.

The JIRA connector supports the following objects:

The Jira/Confluence admin will install an Atlassian Marketplace app with Admin scope (Note that we need Admin scope to fetch permissions associated with Jira objects (see discussion below)) that will be used for indexing the content, and another Connect app that delivers webhooks to the customer’s Glean instance. Installing the Glean Connect app for Confluence will allow the app to read all unrestricted pages in these spaces. It will not be able to read restricted pages unless the admin grants access to the Glean app for those pages.

The JIRA connector for Glean requires specific permissions to function correctly.

The Glean connector for Jira integrates seamlessly with Jira to index data and provide advanced search capabilities across your organization’s Jira projects. To ensure Glean can access the necessary data for indexing while respecting Jira’s permissions and security settings, specific API scopes are required. Two of these scopes require admin-level access. The following will explain why Glean needs admin-level access and follows least privilege.

Granting admin-level permissions for the Glean connector allows Glean to index Jira data securely and effectively, respecting your organization’s permission structures and issue visibility rules. This ensures users only see results they are authorized to access, maintaining both compliance and security.

While “read” permissions allow access to issue content, they do not grant visibility into permission schemes or group memberships, which are crucial for:

Admin-level permissions ensure Glean has the necessary access to these configurations while maintaining alignment with Jira’s security model.

The following Jira REST API scopes necessitate admin-level permissions:

Group/Member Access

Issue Security Schemes and Members

Jira projects often implement granular permissions via groups, members, and security schemes to restrict access to sensitive data. Glean needs access to these configurations to:

Without this data, Glean cannot ensure accurate user results based on their Jira permissions.

Jira’s issue security schemes define visibility rules for issues, often based on user roles, groups, or custom security configurations. Accessing these schemes allows Glean to:

Jira enforces admin-level access for these endpoints because they expose sensitive metadata about:

Disclaimer: The instructions below are updated periodically by Glean on our customer-facing documentation. For the latest instructions, refer to the Glean Admin UI

The identity crawl operates with the following configurations:

The Glean Activity plugin for Jira helps Glean to provide highly personalized search results for the users. By sending webhook events to Glean each time a user views an issue in Jira, the plugin enables Glean instance to gather valuable information that is crucial to delivering an outstanding search experience. This information is stored securely in your dedicated cloud project, ensuring complete privacy and protection of your data.

Content updates for the JIRA connector in Glean can happen quite rapidly, depending on the type of update and the configuration settings. Here are the key areas:

Changes in data must be crawled, processed, and indexed before the data is reflected in the UI. Actual time may vary depending on the number of changes and corpus size. For the most up-to-date crawler refresh information, please refer to [External] Glean crawling strategy

The JIRA crawler follows the traditional crawler strategy, including utilizing the JIRA API and the following ways to get and update data:

Note: If Inclusion (Green-Listing) options are enabled, only content from the Inclusion category will be indexed. If Exclusion (Red-Listing) options are enabled, all content in the exclusion category will be removed. If both rules are applied to the same content, then the content will NOT be indexed, as exclusion rules take priority.

The rules below should be used MINIMALLY to preserve the enterprise search experience, as most end-users expect to find all content. Most customers do not apply any rules or apply exclusion rules sparingly for sensitive folders.

There may be a delay before the system fully reflects these changes. Furthermore, customers can hide the relevant documents if access has been inadvertently granted to an individual. For detailed guidance on using the “Hide” functionality via CSV upload, please refer to How to Hide Documents via CSV Upload article.

By entering specific project ID’s in the box within UI, the specified projects will be excluded from being crawled and indexed by Glean.

Note: Exclusion rules are applied automatically after the next full crawl.

By entering specific project ID’s in the box within UI, the specified projects will be crawled and indexed by Glean (and nothing else)