JIRA

Select the Jira application as a source application type. Leave the default Issues cube name and click Create.

After that, the next screen Select application import options would be opened to continue initial import setup.

Select application import options

On the next page, select which Jira projects you would like to import in flex.bi:

Regular Import Frequency

Specify how frequently you would like to run regular Jira issues import. This will process created and modified issues since last import:

You can select "Every day", "Every hour", "Every 20 minutes" and similar options. The import will be processed 24h, 1 h or 10 minutes etc. after last import (manual or regular). If you would like to run the import every day at a particular time, select "Daily at specified time" option.

JQL Query Filter

If you would like to analyze a subset of issues from selected projects, you can specify a JQL query that would limit which issues 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

Statuses and history

In the Statuses and history section select if you would like to import issue change history, remaining estimated hours history and Age and Resolution Intervals dimensions, as well as indicate Issues closed measure.

Option "Import issue change history" also should be selected if you want to import custom field changes (should be used together with option "Import value changes" for the custom field).

Time dimension 

You can specify the time zone, the first day of the week and non-working days of the Time dimension.

You can use only one time zone in each flex.bi account. The time zone of the Time dimension will be used to determine the date member in the Time dimension when importing issue measures (e.g. Issues created, Issues resolved and others) and issue properties. If a time zone is not specified then the default Jira server time zone will be used. If a different time zone will be selected then all date timestamps will be converted to this time zone.

I the first day of the week will be selected then the Time dimension Weekly hierarchy will be updated to use this first day of the week.

Non-working days (standard non-working days of the week and additional non-working days / holidays) will be used to calculate the new workdays measures – Average resolution workdays, Average age workdays, Workdays in transition status, Average workdays in transition status. Non-working days of the Time dimension will be used also for DateDiffWorkdays and DateAddWorkdays MDX functions as a default non-working days argument.

If you have a long list of additional non-working days then you can copy the list and paste in the time dimension options for the different flex.bi account.

Jira Custom Fields

If you would like to import Jira custom fields then click Show available custom fields link in the Custom fields section and select custom fields you would like to import. Select either individual checkboxes (Import as a dimension, Import as a measure, Import as a property, or Import value changes) or click on a custom field name to select all available checkboxes for this custom field. Available import options depend on the custom field type or advanced settings for the custom field (if applied).

Select Import as dimension if you want to analyze total numbers by the custom field values (usually, these custom fields are used to classify issues by some parameter). If the custom field is specific for each issue and you just want to get this information when looking on a particular issue, import it as property. 

If you want to get totals of numeric or date fields import them as measures. In the result, a set of measures with totals of custom field numeric values or measures with custom date fields would be created.

If you want to see how numeric custom field values are changed over time, then import value changes.

After specifying import options click Import to start Jira issues import background job.

In Source Data tab you will see the current status of Jira import background job, as well as additional information - when the data cube was created, projects imported in this cube, imported projects and user whose credentials are used to authorize Jira for data import.

If you have many Jira issues and have selected many custom fields for import then initial import might take a longer time to complete. In Status column you will see how many issues have been imported so far to estimate completion time.

Incremental import

After each successful Jira issues import, flex.bi will store a timestamp for processed Jira issues.

During regular Jira data import (either manual or automatic), flex.bi will import only those Jira issues which have been created, updated, or deleted since the last import. 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), flex.bi will force a full re-import of all Jira issues.

Reset authorization

When the user who had initially authorized Jira for data import (i.e. her Jira credentials were used to detect which projects and fields could be imported in this flex.bi account during the first Jira data import into this account) is not available anymore or does not have permissions to needed project, data source authorization could be reset to another user.

The new user has to be added to the account with Owner, User Admin or Data Admin account user roles. She should log in flex.bi, open Source tab and click Reset authorization.

After approving this action, the Status will be changed to "Authorized" and username of the new user will be visible under Source selection. 

Open Edit import settings to select projects and custom fields available for the new user and perform data import.