Use Jira Software As a Content Source
SearchUnify can index the issues stored in Jira Software instances. This article walks you through the process of setting up Jira Software as a content source.
You should have access to the projects or spaces to be crawled. Ensure that you have Project Administrator access. This access is required to fetch the permission schema in Jira.
You must have “Browse Users and Groups” permission. You must be in a group that has global permissions of “Browse Users and Groups” in Atlassian. This is needed to fetch the email and account id of the user to respect permissions.
The number of responses received from Jira over a given period depend upon the Jira's rate limits. You can find the the latest rate limits on their website.
Establish a Connection
- Navigate to Content Sources.
- Click Add New Content Source.
- Find Jira from the search box and click Add.
- Give your content source a Name.
- Enter the web address of your Jira Software instance in Client URL.
- Select an Authentication Method.
Select the content language and click Connect. If your clients report issues in German, select -de and for French pick -fr. It's possible to set multiple content languages. The default content language is English (-en).
Set Up Crawl Frequency
The first crawl is always manual and is performed after configuring the content source. For now, keep the frequency to its default value Never and click Set and move to the next section.
Select Fields for Indexing
You can index all
issue content fields or only a few of them.
- Click to select content fields.
- From the leftmost column Name add content fields one at a time.
- Once you have finished, click Save.
- Navigate to By Projects.
- Use the index to find your project and check enable for each one of it. If no project is selected, then all the projects are crawled.
- Press Save.
After the First Crawl
Return to the Content Sources screen and click in Actions. The number of indexed documents is updated after the crawl is complete. You can view crawl progress in in Actions. Documentation on crawl progress is in View Crawl Logs.
Review the settings in Rules if there is no progress in Crawl Logs.
For Mamba '22 and newer instances, search isn't impacted during a crawl. However, in older instances, some documents remain inaccessible while a crawl is going on.
Once the first crawl is complete, click in Actions open the content source for editing, and set a crawl frequency.
- In Choose a Date, click to fire up a calendar and select a date. Only the data after the selected date is indexed.
- Use the Frequency dropdown to select how often SearchUnify should index the data. For illustration, the frequency has been set to Weekly and Tuesday has been chosen as the crawling day. Whenever the Frequency is other than Never, a third dropdown appears where you can specify the interval. Also, whenever Frequency is set to Hourly, then manual crawls are disabled.
- Click Set to save crawl frequency settings. On clicking Set, you are taken to the Rules tab.
Data Deletion and SU Index
A method to update the index in real time is to enable event subscriptions, which supplement existing crawls and synchronize data between your Jira instance and SearchUnify in real time. The instructions are on Synchronize SearchUnify Index with Jira through Event Subscription
If your organization uses Jira On-Premises, write to your customer support representative. They will share with you a list of SearchUnify IPs to be whitelisted. Once the IPs have been whitelisted, SearchUnify can crawl the data in your Jira instance.
Last updated: Tuesday, February 6, 2024
Or, send us your review at firstname.lastname@example.org