Before proceeding with these steps, you must coordinate with the Glean Support team to complete the necessary actions, such as updating the configuration file and setting the webhook and plugin target URLs.
1. Install the Webhook App
- In the Jira UI, click on the ⚙️ icon at the top right and select System.
- Under the Advanced section, select Webhooks.
- Click Create a webhook.
- Fill in the form as follows:
- Name:
Glean Search - Status:
Enabled - URL: Webhook URL provided by the Glean representative
- Events:
- Comment created
- Comment updated
- Comment deleted
- Issue created
- Issue updated
- Issue deleted
- Exclude body: Ensure the checkbox is not selected.
- Name:
- Save the webhook configuration.
2. Install the Glean Plugin
- Download the Glean Activity Plugin from the Atlassian Marketplace.
- Refer to the following table for proper version installation:
| Jira DC Version | Glean Plugin Version |
|---|---|
| < 9.0.0 | < = 1.6.1 |
| >= 9.0.0 and < 10.0.0 | 1.7.0 |
| >= 10.0.0 | >= 2.0.0 |
- Follow the installation instructions provided on the marketplace page.
3. Configure the Glean Plugin
- Go to the Jira Administration Console (⚙️ icon at the top right).
- Select Manage apps.
- In the left navigation pane, there should be Other section visible.
- Go to Configure events target URL for Glean Search Plugin.
- If the option is not visible, ensure the plugin was installed correctly.
- Set the Plugin Target URL provided by the Glean representative.
- Go to Configure Service Account for Glean Search Plugin.
- Set the email of the service account user you want to use.
4. Configure the Jira Datasource in Glean
- Go to the Data Sources tab in the Glean Admin Console.
- Search for Jira Server and open the Setup Page.
- Configure the datasource by providing the required details.
Ensure the email configured in the Glean plugin matches the username/password configured here. Both must belong to the same user.
Caveats
- The service account should still have Browse Issues permission to all the projects to be able to crawl all issues .
- The service account should still have Browse users and groups global permission to be able to run the crawler.