All eazyBI for Jira eazyBI for Confluence Private eazyBI

Jira custom fields
eazyBI for Jira

You can import Jira issue custom fields from any project (company-managed or team-managed). 

How to import custom field

By default, eazyBI does not import custom fields. You must select which fields you want to include in your reports. Custom fields are available in Jira import options: use the Add-ons tab to select custom fields from Jira apps, and Custom fields tab to select other Jira custom fields. 

You can import custom fields as dimensions, measures, and properties; the available options depend on the custom field type. For some custom field types, you can also import value changes. The following chapters describe how each custom field type is represented in eazyBI and how you can use it in the reports.

Free text custom fields

The main purpose of free text fields in Jira is to capture additional, issue-specific, or other uncategorized information, similar to the description field. In these types of fields, values are often long texts that can be descriptive but are not great for grouping or filtering the issue.

Considering the nature of the field value, eazyBI lets you import them as property. 

eazyBI supports importing data from the following text fields:

When this type of field is selected and imported, eazyBI creates the value in measure "Issue <text field name>," which represents the text value when using the Issue dimension in the report and shows results at the issue level.

For example, if you have the text field "Description from Customer", eazyBI creates the property "Issue Description from Customer". You can select this property from the Measures.


Date custom fields

The main purpose of the Date and DateTime custom fields in Jira is to enter the date or time. These fields have specific formats and validation, and the user can pick just one value per issue.

Considering the nature of the field value, eazyBI lets you import them as property and measure. Additionally, you can import the value changes to see a comma-separated list of previous values.

eazyBI supports importing data from the following field types:

When this type of field is selected and imported as a measure, eazyBI creates several measures:

It is not possible to import date and datetime fields as dimensions in eazyBI. In eazyBI, there is one Time dimension, and in combination with a measure ("Issues with <custom date field name>"), it groups data by a date related to that measure. 


When this type of field is selected and imported as property eazyBI creates the value in measure "Issue <custom date field name>" which represents the current date value when using the Issue dimension in the report and shows results at the issue level.

If you select to import also "value changes", eazyBI creates an additional property "Issue <custom date field name> old values" that shows comma-separated list of previous values issue had before the current value.

For example, if you have the single-choice field "Start date", eazyBI creates the property "Issue Start date" and property "Issue Start date old values". You can select this property from the Measures to show the current Planned start date for each issue

Number custom fields

eazyBI supports importing data Jira Number Field custom field. The main purpose of the Number custom fields in Jira is to enter the quantitative value. The field may contain only numeric values including floating point numbers.

Considering the nature of the field value, eazyBI lets you import them as property and measure. Additionally, you can import the value changes to see historical values when used with the Time dimension.

When this type of field is selected and imported as a measure, eazyBI creates several measures:

When this type of field is selected and imported as a value changes, eazyBI creates several measures:

The value change measures can be used with dimensions with imported value changes, like Issue Type, Assignee, Resolution, Sprint, etc. (see more Import issue change history).

For example, if you import a Number field "Planned capacity," eazyBI will create the following measures: Planned Capacity created, Planned Capacity due, Planned Capacity resolved, Planned Capacity closed, Planned Capacity with due date, Planned Capacity with planned start date, Planned Capacity change, Planned Capacity history. And 6 hidden measures: Issues with Planned Capacity created, Issues with Planned Capacity due, Issues with Planned Capacity resolved, Issues with Planned Capacity closed, Planned Capacity added, and Planned Capacity removed.

In addition to measuring checkbox selection for the number custom field, you can also import it as a dimension to see issue distribution by custom field value or interval dimension to make histograms.

See advanced settings for custom fields on how to enable data import as an interval dimension.

Single-choice custom field

The main purpose of single-choice fields in Jira is to group and categorize issues. In these types of fields, values are predefined, and the user can choose only one value per issue.

Considering the nature of the field value, eazyBI lets you import them as dimension and property. Usually, we recommend selecting both checkboxes for this type of custom fields

eazyBI supports importing data from the following single-choice fields:

When this type of field is selected and imported as dimension, eazyBI creates a new dimension with the same name as the custom field, and dimension members are created from current custom field values used for imported issues in eazyBI data cube.

When this type of field is selected and imported as property eazyBI creates the value in measure "Issue <text field name>" which represents the text value when using the Issue dimension in the report and shows results at the issue level.

For example, if you have the single-choice field "T-shirt size", eazyBI creates the property "Issue T-shirt size" and dimension "T-shirt size". You can select this property from the Measures to show the current T-shirt Size value for each issue, and a dimension "T-shirt Size" to filter results.


For this custom field type, in addition to dimension checkbox selection, you can also import the change history and extend it with the additional data. 

Multi-choice custom field

The main purpose of multi-choice fields in Jira is to group and categorize issues. In these fields, values are predefined in most cases except for "labels" fields, and the user can choose multiple values per issue.

If several values are specified for an issue, then measures in the report are counted for each matching value.

Considering the nature of the field value, eazyBI lets you import them as dimensions and properties. We usually recommend selecting both checkboxes for this type of custom field.


eazyBI supports importing data from the following multiple-choice custom fields:

When this field type is selected and imported as a dimension, eazyBI creates a new multi-value dimension with the same name as the custom field. Dimension members are created from current custom field values used for imported issues in the eazyBI data cube. Each value from the multiple choice field is independent of another value, so the eazyBI measures in the report are counted for each selected value. Therefore, we recommend filtering or selecting only one dimension member at a time. However, if it is necessary to select or combine multiple members, we suggest using distinct measures.

When this type of field is selected and imported as property, eazyBI creates the value in measure "Issue <custom field name>," which represents the issue field all values in comma-separated string when using the Issue dimension in the report and shows results at the issue level.

For example, if you have the multiple choice field "Custom labels", eazyBI creates the property "Issue Custom labels" and dimension "Custom labels". You can select this property from the Measures and analyze results also by the particular dimension.

eazyBI does not support importing change history or additional data for multi-choice custom fields.

Additionally, you can apply custom field advanced settings to create an additional CSV dimension and analyze all applied combinations for imported issues as comma-separated strings.

Cascading fields

eazyBI supports importing data Jira Cascading Select custom field.

The main purpose of cascading fields in Jira is to group and categorize issues with values from two select lists. In these fields, values are predefined, and the user can choose one value from each list.

Considering the nature of the field value, eazyBI lets you import them as dimension and property. Usually, we recommend selecting both checkboxes for this type of custom fields.

When this field type is selected and imported as a dimension, eazyBI creates a new dimension with two hierarchy levels where the value from the first list is in a higher level and value from the second list is in lower level. Dimension members are created from current custom field values used for imported issues in the eazyBI data cube. By default, the (none) member to group issuses without value is created only at the first hierarchy level; but you can add custom field advanced settings to make (none) member for each hierarchy level.

When this type of field is selected and imported as property, eazyBI creates the value in measure "Issue <custom field name>," which represents the issue field both values separated by a dash ("-") when using the Issue dimension in the report and shows results at the issue level.

For example, if you have the cascading field "Business Unit and Department," eazyBI creates the property "Issue Business Unit and Department" and dimension "Business Unit and Department". You can select this property from the Measures and analyze results also by the particular dimension. This dimension will have automatically two levels (First, Second) in the hierarchy and you can filter report by each of them.

eazyBI does not support importing change history and additional data for cascading custom fields

Can not find my custom field 

You can import Jira issue custom fields for the Jira source application. eazyBI detects most types of Jira issue custom fields automatically, and you can select them from the import options page. But there might be cases when some fields are not listed in the Custom fields tab:

If you have the custom field imported, but some values are missing in reports, check that the missing value is applied for at least one issue in Jira and the issue is imported into the eazyBI account.