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.
Measures 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.
Issues data cube contains the following measures:
|Issues created||Total number of created issues that matches selected dimension members. If the Time dimension is used then Issues created are grouped by issue creation dates and shown in the corresponding time period.|
|Issues due||Due (or unresolved) issues which do not have resolution and resolution date. On the Time dimension they are grouped by issue due dates (if issue do not have due date then number of these issues will be counted only in All Times member).|
|Issues resolved||Resolved issues which have resolution and resolution date. On the Time dimension grouped by issue resolution dates.|
|Issues with due date||All issues (both due and resolved) which have a due date specified. On the Time dimension grouped by issue due dates.|
|Issues last updated||Total number of issues that matches selected dimension members. If the Time dimension is used then Issues last updated are grouped by issue updated dates and shown in the corresponding time period.|
|Original estimated hours||Total of original estimated hours. On the Time dimension grouped by issue creation dates.|
|Remaining estimated hours||Total of current remaining estimated hours. On the Time dimension grouped by issue due dates for unresolved issues and by resolution dates for resolved issues.|
Total of hours spent for issues matching the selected dimension members. The Logged by dimension can be used to see hours spent by individual users.
|Total number of sub-tasks for parent issues that matches selected dimension members.|
Read also about additional Issues closed measure and how to use it.
Distinct issues count
|Issues created count|
Issues due count
Issues resolved 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 selected components then "Issues created" value will be 2 but "Issues created count" value will be 1 for this issue.|
|Issues with hours spent||Distinct count of issues which have any hours logged in the selected Time period.|
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.
The following standard calculated measures are available:
|Open issues||Calculates number of unresolved issues at the end of corresponding Time dimension period (as Issues created minus Issues resolved since beginning of the time until end of the selected time period).|
|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, that returns a pre-calculated number of days from created to resolved dates, is used in 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, that returns a pre-calculated number of days from created to closing dates, is used in 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.|
|Original estimated hours|
Remaining estimated hours
Hours spent with sub-tasks
Similar to Original estimated hours, Remaining estimated hours, Hours spent measures but includes also estimated and actual hours of sub-tasks of selected issues.
Measures with the suffix "with sub-tasks" should be used only for "Issue" dimension hierarchies with "Sub-task" level members, otherwise, they might mislead you
Properties are calculated measures retrieving a specific information for each particular dimension member. Some of properties are also available as dimensions (Issue type, Status) to analyze data by or are related to measures (Issues creation date is related to measure Issues created or property Issue Story points are related to 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 created date|
Issue updated date
Issue resolution date
Issue due date
|If 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.|
|Issue parent key|
Issue sub-task keys
Issue open sub-task keys
|Also can be used if Issue dimension detailed issues are placed on rows.|
|Can be used if Project dimension (at project or component level) is placed on rows.|
|Version release date||Can be used if Affects Version or Fix Version dimensions are placed on rows.|
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 Project level which can be expanded to Component level to see all components of project. If issue is assigned to several components then it will be counted for each component but only once for the whole project. The a secondary hierarchy in the same "Project" dimension which also aggregates projects by Project Category.|
|Reporter||Users who reported issues.|
|Assignee||Current assignee user for issues.|
|Issue Type||Current issue type.|
|Priority||Current issue priority.|
|Status||Current issue status. This dimension has a secondary hierarchy which aggregates members into Status Category|
|Resolution||Current (last) resolution if present.|
|Affects Version||Current affects versions of an issue which 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 project. This dimension has multiple hierarchies to choose from.|
|Fix Version||Current fix versions of an issue which 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 project. This dimension has multiple hierarchies to choose from.|
|Issue||List of all individual issues, grouped by Project hierarchy level. 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.|
|Label||Current labels of issue. If several labels are specified for an issue then measures will be counted for each label.|
Standard time dimension with Year / Quarter / Month / Day hierarchy and weekly hierarchy with Year / Week / Day levels.
Can enable (add) fiscal time hierarchy with Fiscal year / Fiscal Quarter / Month / Day and define the first month of the fiscal year. Fiscal hierarchy year and quarter member names are referenced by the year in which the fiscal year ends.
Logged by Group
Corresponding Jira user groups of reporters, assignees or logged by users. If a user belongs to several Jira user groups then corresponding measure value will be included for all corresponding user groups in the user group dimension.
Corresponding interval dimension of issues age from issue created date till now and for resolved issues by resolution days. Intervals for this dimension can be changed by report users based their eazyBI user roles.