Data from Jira
eazyBI for Jira
On this page:
Initial Import
After creating an eazyBI account, you need to import into the eazyBI database the selected Jira project issues (or space work items in Jira Cloud) that you would like to analyze. You can edit import options at any time.
From the Source Data tab, select Add new source application and then select the Jira application as a source application type.
The data import from Jira is authorized by the user who performs the initial data import: their Jira credentials are used to detect which projects (or spaces in Jira Cloud) and fields could be imported into this eazyBI account and are applied to all consecutive data imports–scheduled or manual. Inactive or non-existent users can't authorize data import: if the user's access rights in Jira change (the user is deactivated or loses access to some of the selected projects), user authorization must be reset.
After that, the next screen, Select application import options, would be opened to continue the initial import setup.
Select application import options
Select which Jira projects (or spaces in Jira Cloud) you would like to import into eazyBI. You can select all or individual projects, hide unselected ones, and clear the selection [1]. You can use the search filter to find your project [2] or choose between projects and categories when selecting data for import [3]. When a project category is changed in Jira, the project will be automatically deselected from the eazyBI import if the new category isn't selected.
During data import, eazyBI automatically pulls data from Jira standard fields such as Issue Type, Priority, Label, Fix version, Assignee, and a few others. Here is the list of all dimensions and measures. You don't need to select and import them separately. eazyBI provides additional import options for Software and Service Management project types.
The option to keep archived project data is available on Cloud and eazyBI version 9.0.
You can preserve the data of archived projects in the eazyBI account if the project data was imported into this account before the project was archived [4]. For archived projects, eazyBI keeps previously imported data but does not update or recalculate it during data imports. The archived project list varies for each account based on previously selected projects:
- If the project is archived and hasn't been imported into the specific account before archiving, it won't appear in the archived project list.
- If you deselect the archived project in the data import, eazyBI will remove this project's data during the import, and it won't appear in the archived project list anymore.
- If you empty the cube, then the archived project data are deleted, and it won't appear in the archived project list anymore.
By default, data imports from Jira are scheduled once a day, but you can adjust the scheduler. Jira Cloud customers can also schedule imports more often with Process events.
Statuses and history
In the Statuses and history section, select if you would like to import issue change history [1] as well as indicate Issues closed measure [2].
Option "Import issue change history" should also be selected if you want to import custom field changes (use it together with the option "Import value changes" for custom fields and Sprints).
Process events
Available only in eazyBI for Jira Cloud
When Process events are selected, eazyBI listens to the most essential Jira Cloud webhooks and updates data every hour, even if the Regular import runs once a day.
Process events import data on:
- Issue changes - creation, deletion, or update (when the issue’s updated date is changed);
- Worklog changes - creation, deleted, or updated;
- Comment changes - created, deleted, or updated;
- Issue link changes - added, deleted;
- Sprint changes - deleted, updated, started, and completed;
- Sprint board configuration changes.
However, process events might not capture changes from Jira calculated fields and Jira apps (Tempo Planner, Xray, Zephyr Squad, etc.) because these changes are not received via webhooks.
Initiate data import by pressing the "Import" button from the Source Data page, or wait till the closest regular incremental import to get data from Jira apps.
When making any changes in the import options page for the Jira source application, you must press the "Import" button to restart process events.
Add-ons
In the Add-ons tab, select to import custom fields specific to Jira apps. Some Jira apps require additional authorization and configuration.
You can install additional add-ons from the eazyBI Marketplace. If your app isn't available yet, build it using a coding AI agent.
Custom fields
In Custom fields tab, you can select the custom fields you need, including custom fields from company-managed and team-managed projects. Depending on the custom field type, you can import a custom field as a dimension, measure, or property, and import its value changes. For details on each custom field type and its import options, see the Jira custom fields page.
Global calculated fields in eazyBI appear in the custom field list among Jira custom fields. Account-specific calculated fields in eazyBI appear in a separate section, Calculated Custom fields, at the bottom of the page.
eazyBI does not import work item links by default. Use the Issue links section to specify which issue links to import: as a dimension of linked issues, or as an issue property with a comma-separated list of linked issue keys. For details and examples, see the Import issue links page.
Import only the custom fields you need for analysis. Each additional custom field increases the import time.
Additional import options
In additional import options, you can configure the Time dimension and enable Sample reports. The following chapters explain Jira source application-specific import options.
JQL query filter
If you would like to analyze a subset of issues from selected projects (or spaces in Jira Cloud), you can specify a JQL query that would limit which issues (or work items in Jira Cloud) are imported.
- To not import issues that have been closed for more than one year, you can use JQL
status not in (Closed) OR updatedDate > -52w - To import issues that do not have any security level, use JQL
level is empty - To limit by a saved Jira filter
filter = "Name of saved Jira filter"(the filter must be available to the user who authorized the data import from Jira)
It is not allowed to use the "ORDER BY" clause of the JQL query in eazyBI. The data import implementation uses its own ordering of issues.
eazyBI recognizes only functions from the Jira advanced searching list. Enhanced search by Scriptrunner and functions provided by other applications are not applicable in eazyBI import options. In those cases, you should use saved Jira filter names in the eazyBI import options page.
We recommend limiting imported versions and components when using JQL filters to import only relevant components, fix versions, and affects version in the data cube.
Additional dimensions for user groups, intervals, and issue link fields
You can import user project roles for Assignee and Reporter and user groups for Assignee, Reporter, Logged by, or Transition author and specify set of groups you would like to use in your reports [1].
Select the option to import Age and Resolution Intervals dimensions [2] if you want to create reports by unresolved issue age intervals or Issue resolution intervals.
If you use issue hierarchy in the reports and would like to see issue data at one hierarchy level while filtering by another, you might want to import the issue link field dimensions [3]. For example, get all data by Fix version of the related Epic.
Additional measures for time tracking
If you would like a broader set of time-tracking measures, select the option to import additional measures for hours spent and original estimated hours.
Template account
Select Template account [1] to import reports, dashboards, and calculated measures defined in a common template account. You can override [2] existing reports, dashboards, and calculated measures with reports, dashboards, and calculated measures from the template account.
Incremental import
After each successful Jira issues import, eazyBI will store a timestamp for processed Jira issues.
During a regular Jira data import (manual or automatic), eazyBI will import only Jira issues that have been created, updated, or deleted since the last import. All issues from archived projects, as well as archived issues, will automatically be removed from the "Issues" data cube. Incremental Jira data imports are much faster than the initial import.
If you change import options (for example, add an additional project or select additional custom fields), eazyBI will force a full re-import of all Jira issues.
The user can initiate the incremental import by manually pressing the Import button from the Source Data screen. By default, the Source Data page is available only to eazyBI account users with the data roles of Owner, User admin, and Data admin. But you can enable the option to start incremental import for the Report admin and User roles, too. This option cannot be combined with any data access roles. If the users can initiate incremental imports, they have unrestricted access to the data imported into the account.
The option to start an incremental import manually by the Report admin or User is available in eazyBI for Jira Cloud, starting with eazyBI version 8.2.
Adjust imported data
Users with data admin or higher role can edit import options and delete imported data.
- Delete members without data
- Re-import all data
- Reset authorization
- Rename data cube
- Empty cube and re-import data
- Export source application definition
Delete members without data
You can delete members without data from dimensions in the Issues cube on Cloud, starting with eazyBI version 8.1.
You can delete members with no data from the Issues cube for the following dimensions:
- Jira dimensions: Assignee, Reporter, Logged by, Priority, Issue Type, Status, Resolution, Security Level, Label, Worklog, Sprint, Transition Status, Transition, Transition Author;
- Jira custom field: single-choice custom fields imported with separate_table settings enabled.