All eazyBI for Jira eazyBI for Confluence Private eazyBI

Jira Core measures and dimensions
eazyBI for Jira

On this page:

Jira core measures and dimensions represent issue workflow and standard fields and are available if you have any of Jira products - Jira Work Management (Jira Core on Data Center), Jira Software, or Jira Service Management. If you would like to analyze also product-specific fields, such as story points or SLA breaches, please see product-specific pages: Jira Software or Jira Service Management.

 

In Jira, all data are stored around issues.

The eazyBI data cube is made up of Dimensions and Measures.

During data import to eazyBI, Jira issue information is reorganized and grouped into that structure.

All numerical values like created or resolved issue counts and original estimates are imported as Measures.

Listed values - issue statuses, priorities, users, versions, etc - are imported as Dimensions.

All values are also imported as properties for each particular issue.

All dimensions are displayed in a Dimensions area. They are used to analyze measures by different features.

Measure is a specific dimension.

A part of measures is stored during data import based on events happened to issues, like, issue creation, resolution or logged work.

eazyBI is using them to calculate a bunch of other popular metrics, you can use them as well to create your own measures!

Issue properties are specific measures that hold information about each individual issue and is used to display in the issue list.

To create a report, combine Dimensions and Measures.

Measures will be calculated accordingly to each dimension member or combination selected in the report.

Now you know how Jira issue data are restructured in eazyBI dimensions and measures.

Measures

Issues data cube contains the following predefined measures:

Issues created

A total number of created issues that match selected dimension members. If the Time dimension is used then Issues created are grouped by issue creation dates.

Issues due

Due (or unresolved) issues that do not have a resolution date. Used with the Time dimension, issues are grouped by issue due dates (if an issue does not have a due date then it is counted only to the All Times member).

Issues resolved

Resolved issues that have a resolution date. Used with the Time dimension, grouped by issue resolution dates.

Issues closed

Read also about additional Issues closed measure and how to use it. If the Issues closed measure is imported then also Issues closed count will be in this group. If Import issue change history is selected then also Transitions to status issues count and Transitions from status issues count will be in this group.

Open issues

Calculates a number of unresolved issues at the end of the corresponding Time dimension period (as Issues created minus Issues resolved since the beginning of the time until the end of the selected time period).

Issues with due date

All issues (both due and resolved) which have a due date specified. Used with the Time dimension, grouped by issue due dates.

Issues last updated

A total number of issues that match selected dimension members. If the Time dimension is used then Issues last updated counts issues by the last update date and shows the total count in the corresponding period.

Sub-tasks created

Sub-tasks due

Sub-tasks resolved

A total number of sub-tasks for parent issues that match selected dimension members.

Use those measures in reports and calculations in case you need to apply filters on parent issues only and then get the count of their sub-tasks; otherwise, use corresponding measures Issues created, Issues due, and Issues resolved (they include values for all level issues, parent and sub-tasks, based on the report context).

Average resolution days

Calculates average resolution days of resolved issues (that are counted in Issues resolved) and are grouped by issue resolution date on Time dimension.
Hidden Total resolution days Measure, which returns a pre-calculated number of days from created to resolved dates, is used in the Average resolution days formula.

Average resolution workdays

Similar to Average resolution days but only workdays are calculated according to Time dimension options.

Average closing days

Calculates average closing days of closed issues (that are counted in Issues closed) and are grouped by issue closing date on Time dimension.
Hidden Total closing days Measure, which returns a pre-calculated number of days from created to closing dates, is used in the Average closing days formula.

Average age days

Calculates current average age days of unresolved issues (that are counted in Issues due) and are grouped by issue due date on Time dimension.

Average age workdays

Similar to Average age days but only workdays are calculated according to Time dimension options.

Measures representing Issue change history, like Transitions to status, Issues history, Transitions to assignee, etc., are described on Import issue change history page.

Measures representing estimates and logged hours, like Hours spent, Original estimated hours, and Remaining estimated hours, are described on Time tracking measures page.

Distinct issues count

Issues created count

Issues due count

Issues resolved count

Issues closed count

In Distinct issues count measure group distinct (unique) count of issues is calculated. These measures can show a different result than previously described Issues created, due and resolved measures in a case when some multi-value dimension with a multiple-member selection is put on pages (e.g. Project components or versions or multi-value custom fields). E.g. if several components are selected and one issue belongs to two of the selected components then Issues created value will be 2 but Issues created count value will be 1 for this issue.
If Issues closed measure is imported then also Issues closed count will be in this group. If Import issue change history is selected then also Transitions to status issues count and Transitions from status issues count will be in this group.

Properties

Properties are calculated measures retrieving specific information for each particular dimension member. Some of the properties are also available as dimensions (Issue Type, Status) to analyze data by or are related to measures (Issues created date is related to measure Issues created or property Issue Story points are related to a measure Story points created), while some of them are available only as properties (Project lead).

To get a property value displayed in the report, you should use dimension members of the corresponding dimension in the report rows: Issue dimension Issue level members if issue properties should be displayed, Fix version or Affects version Version level members if version properties should be displayed, etc. 

Property values are displayed empty for higher-level members or if other dimensions are selected in rows. It is also true for calculations where properties are used in the formula.

Property names usually start with the name of the corresponding dimension: Issue .... , Project .... , Version .... .

Issue properties

Issue created date

Issue updated date

Issue resolution date

Issue due date

Issue reporter

Issue assignee

Issue type

Issue priority

Issue status

Issue resolution

Issue affects versions

Issue fix versions

Issue components

Issue labels

If the Issue dimension is placed on rows and expanded to detailed issues and these measures are placed on columns then detailed creation, updated, resolution and due dates, as well as reporter, assignee, type, priority, status, and resolution of issues are shown.

For team-managed projects, property Issue type value is a combination of issue type and project key, like "Story (DEMO)". Also, property Issue status value is a combination of status and project key, like "In Progress (DEMO)".

Issue parent key

Issue sub-task keys

Issue open sub-task keys

It also can be used if Issue dimension detailed issues are placed in rows.
Other properties

Project lead

Component lead

It can be used if Project dimension (at project or component level) is placed on rows.

Version release date

It can be used if Affects Version or Fix Version dimensions are placed in rows.

Dimensions

Measures and calculated measures can be analyzed by the following dimensions. Some dimensions contain multiple hierarchies but only one hierarchy from a dimension can be used in the report.

Project

Both hierarchies in Project dimension contain a Project-level which can be expanded to the Component level to see all components of the project. If the issue is assigned to several components then it will be counted for each component but only once for the whole project. The secondary hierarchy in the same Project dimension which also aggregates projects by Project Category.

There is an option to create custom hierarchies with the Add custom hierarchy. It is possible to create a hierarchy based on Project property Project lead or custom project properties imported with additional data import.

Reporter

Users who reported issues.

There is an option to create custom hierarchies with the Add custom hierarchy. It is possible to create a hierarchy based on custom Reporter properties imported with additional data import.

User dimension members have several properties available. For, example Email, Jira user group. You can display properties for user-level members using the function Get in calculated measure.

Assignee

Current (last) assignee user for issues. When used with measures representing change history, shows the issue assignee at the time.

There is an option to create custom hierarchies with the Add custom hierarchy. It is possible to create a hierarchy based on custom Assignee properties imported with additional data import.

User dimension members have several properties available. For, example Email, Jira user group. You can display properties for user-level members using the function Get in calculated measure.

Issue Type

Current (last) issue type. When used with measures representing change history, shows the issue type at the time.

For team-managed projects, issue type value is a combination of issue type and project key, like "Story (DEMO)". eazyBI also creates a secondary hierarchy By Name that groups issue types first by issue type name and then by project-specific issue types thus allowing to analyze all issues with the same issue type name across all team-managed and standard projects.

Priority

Current issue priority. When used with measures representing change history, shows the issue priority at the time.

Status

Current issue status. This dimension has a secondary hierarchy that aggregates members into Status Category.

For team-managed projects, issue status value is a combination of status and project key, like "In Progress (DEMO)". eazyBI also creates a secondary hierarchy By Name that groups issue statuses first by status name and then by project-specific status thus allowing to analyze all issues with the same status name across all team-managed and standard projects.

Resolution

Current (last) resolution if present. When used with measures representing change history, shows the issue resolution at the time.

Affects Version

The current affects versions of an issue that are grouped at Project and Status levels. If several affects versions are specified for an issue then it will be counted for all versions but only once for all projects. This dimension has multiple hierarchies to choose from.

Fix Version

Current fix versions of an issue that are grouped at Project and Status levels. If several fix versions are specified for an issue then it will be counted for all versions but only once for all projects. This dimension has multiple hierarchies to choose from.

Issue

List of all individual issues, grouped by Project hierarchy level. The Issue dimension typically is not used for summary reports but can be used to drill report selected results cell across Issue dimension Issue level to see all individual issues which are counted in some total. This dimension can have more than two hierarchies (for example, if Epic is imported)
It is also possible to establish additional hierarchies in this dimension (if Issue links used in Jira).

Logged by

Users who have logged hours. To be used with the Hours spent measure.

There is an option to create custom hierarchies with the Add custom hierarchy. It is possible to create a hierarchy based on custom Logged by properties imported with additional data import.

User dimension members have several properties available. For, example Email, Jira user group. You can display properties for user-level members using the function Get in calculated measure.

Label

Current labels of issue. If several labels are specified for an issue then measures will be counted for each label.

Time

Standard time dimension with Year / Quarter / Month / Day hierarchy and weekly hierarchy with Year / Week / Day levels. 

There is an option to create custom hierarchies with the Add custom hierarchy. It is possible to create a Fiscal hierarchy and Multiple weeks hierarchies.

Week Day

Days of the week. The order of the days is depending on the import settings about the first day of the week.

Reporter Group

Assignee Group

Logged by Group

Corresponding Jira user groups of reporters, assignees or logged by users. If a user belongs to several Jira user groups then the corresponding measure value will be included for all corresponding user groups in the user group dimension.

Go to import options to select user group dimensions for data import. 

Assignee Project Role

Reporter Project Role

NEW

Project role which is directly associated with user representing issue reporter or assignee. Jira user groups associated with project roles are not supported, those users appear under (none) project role.

Go to import options to select user project role dimensions for data import.

Project Role dimensions are available on Cloud.

Age interval

Resolution interval

The Age Interval dimension groups currently unresolved issues by their age from the issue created date till now; resolved issues are included in the (none) member of this dimension.

The Resolution Interval groups currently resolved issues by resolution days from the issue created date till resolution date; unresolved issues are included in the (none) member of this dimension.

Intervals for those dimensions can be changed by report users based on their eazyBI user roles. Read documetnation on Interval dimensions for details how to enable them and modify intervals.

Security Level

Current security level assigned to an issue.

Relative Time periods

When you create a new eazyBI account and import data there will be some predefined calculated members created in the Time dimension. These calculated members can help you with dynamic calculations, for example, to calculate the number of issues resolved in the previous month.

Current month

It finds and returns the member of the Time dimension at the Month level that is the month when the report is being executed. This member is created in a default Time dimension hierarchy and might not work with other hierarchies in Time dimension

Previous month

It finds and returns the member of the Time dimension at the Month level that is one month prior to the month when the report is being executed. This member is created in a default Time dimension hierarchy and might not work with other hierarchies in Time dimension

Last 12 months

It aggregates members from Time dimension at the Month level based between 12 months ago and today (dynamically). This member is created in a default Time dimension hierarchy and might not work with other hierarchies in Time dimension

Last 30 days

It aggregates members from Time dimension at the Day level based between 30 days ago and today (dynamically). This member is created in a default Time dimension hierarchy and might not work with other hierarchies in Time dimension

Current year

It finds and returns the member of the Time dimension at the Year level that is the year when the report is being executed. This member is created in a default Time dimension hierarchy and might not work with other hierarchies in Time dimension

Previous year

It finds and returns the member of the Time dimension at the Year level that is one year prior to the year when the report is being executed. This member is created in a default Time dimension hierarchy and might not work with other hierarchies in Time dimension

Current week

It finds and returns the member of the Time dimension at the Week level that is the week when the report is being executed. This member is created in a weekly Time dimension hierarchy and might work only in this particular hierarchy

Previous week

It finds and returns the member of the Time dimension at the Week level that is one week prior to the week when the report is being executed. This member is created in a weekly Time dimension hierarchy and might work only in this particular hierarchy

Last 4 weeks

It aggregates members from Time dimension at the Week level based between 4 weeks ago and the current week (dynamically). This member is created in a weekly hierarchy for the Time dimension and might work only in this particular hierarchy

eazyBI allows opening and viewing formulas for these calculated members but it would not let you change them. Feel free to copy formulas and adjust them to create your own custom periods for report filtering and calculations.