Uploading Data from Jira

Table of Contents

Everlaw’s Jira cloud connector allows you to upload relevant Jira issues and associated attachments. While using our Jira cloud connector, you will be able to specify the project(s), user(s), and date range of Jira data you would like to collect. 

Uploading data directly into Everlaw from Jira requires having Database Upload permissions on Everlaw and an Atlassian account with access to the Jira site that you would like to collect from. 

To learn more about how Everlaw handles third party data, please consult our privacy notice

Return to table of contents

Collecting data from Jira

To upload your Jira data directly into Everlaw, navigate to the Uploads page and select Native Upload. From there, scroll down and select Jira under “Collect from cloud application.”

Next, you will be prompted to sign in to your Atlassian account. Note the Atlassian account used to log in will need to have access to the Jira site that you want to collect data from.

Once logged in, you will be prompted to select a Jira site that you would like to collect from and authorize Everlaw’s access to the selected site for upload. By selecting a Jira site from the drop-down menu and clicking “Accept,” you are giving Everlaw permission to collect and upload the relevant Jira data (i.e., Jira issues and any associated attachments). Note that any Jira site that you have access to through your Atlassian account will be available in the drop-down menu. 

Once you have authorized Everlaw’s access to a selected Jira site, an upload wizard will appear to guide you through selecting the Jira site that you would like to collect from. From there, you can specify the projects, users, and date range of the Jira issues that you would like to collect.


Selecting a Jira site in this step will allow you to select the projects, users, and dates associated with available Jira issues that you would like to collect from. Note that only Jira sites that you have previously authorized Everlaw to access will be available to be selected in this step. 

After you have selected your Jira site, click Next to move on to the Projects selection step. In this step, you can choose which projects to import Jira data from. To the degree your Atlassian account does not have access to Jira issues in specific projects from the selected Jira site, these projects will be identified in this step with a "NO ACCESS" label and cannot be selected.

After you have chosen your project(s), click Next to move on to the Users selection step. This step displays a list of total users (active, suspended, removed, invited) associated with the selected Jira site. Note that the list of users displayed is independent of the project(s) selected in the previous step.

Selecting users in this step means that you will collect available Jira issues from the project(s) you selected in the previous step that the selected users had a role (creator, assignee, reporter, or commenter). 

After you have chosen your user(s), click Next to move on to the Date range selection step. In this step, you can choose to only import Jira issue data within a certain time frame. When a date range is selected, only Jira Issues created or modified within the selected date range will be included within the upload. If you do not specify a date range, all available Jira issues from your selected project(s) and user(s) will be uploaded by default.

The final step in this upload wizard shows you a summary of your choices. This summary will show your selected Jira site, projects, users, and date range. If you are happy with your selections, click Continue.

You will then be asked to configure your native upload. For more information about native upload settings, read this section of the Native Data Uploads article.

After users finalize the upload configuration, Everlaw will upload and process the data from Jira for review. Please note the following when uploading data from Jira:

  • Users must create PDF images (default setting) as part of their upload configuration or else the data will not be processed correctly for review.
  • The default custodian for Jira objects is the selected Jira site. This default can be overridden for the entire upload with a user-supplied value.

Your upload will be represented as a card on the Native Data page, as well as in the Document Sets column of your home page. To view the cloud upload configuration for a Jira upload, navigate to the relevant upload card on the Native Data page then click the three-dot menu in the top right corner and select “View upload details.” In the resulting dialog, open the “Transferring” tab then expand the source file and select “Show upload configuration.”

For more information about viewing upload details, read this section of the Native Data Uploads article.

Return to table of contents

Reviewing data from Jira

For each Jira Issue uploaded with the Jira cloud connector, Everlaw creates a project-management-typed document displaying information about the Jira Issue in a readable format. The document contains available information associated with a given Jira issue including but not limited to type, status, project name, priority, assignee, creator, reporter, description, timestamps, activity, commenters, watchers, voters, labels, and custom fields. 

 Jira uploads will also include any attachments (e.g., images, videos, etc.) associated with Jira issues that were collected. When reviewing a Jira issue with attachments in the review window, attachments will be shown in the context panel. Attachments can also be grouped with the parent Jira issue in the results table by grouping search results by attachment groups.

Learn more about viewing document groups in the results table.

Return to table of contents



Have more questions? Submit a request


Article is closed for comments.