Jira Core measures and dimensions
- Gvido
Measures
Issues data cube contains the following 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 and shown in the corresponding time period. |
|---|---|
| Issues due | Due (or unresolved) issues that do not have resolution and resolution date. On the Time dimension they are grouped by issue due dates (if issue does not have a due date then it will be counted only in All Times member). |
| Issues resolved | Resolved issues that 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 | A total number of issues that match selected dimension members. If the Time dimension is used then Issues last updated counts issues by last update date and shows total in the corresponding 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. |
Remaining hours | Calculates how many hours are left to reach Original estimated hours when logged time is less than planned. Based on Original estimated hours and Hours spent. Suggested use case - without Time dimension. The measure might not work correctly with Time dimension. |
Remaining overestimated hours | Calculates how many hours will go over Original estimated hours when logged time and remaining estimated time is over planned. Based on Original estimated hours, Remaining estimated hours, and Hours spent. Suggested use case - without Time dimension. The measure might not work correctly with Time dimension. |
Hours spent | Total of hours spent on issues matching the selected dimension members. The Logged by dimension can be used to see hours spent by individual users. You can Drill through cell to get a list of all worklog entries constituting particular Hours spent total value, with additional information -user name, date, issue key, worklog comments, as well as logged hours for this entry. The list could be exported to file. If you use the Tempo app in Jira Cloud, please see how to enable worklog import. |
Sub-tasks created Sub-tasks due Sub-tasks resolved | A total number of sub-tasks for parent issues that match 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 that 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.
Calculated measures
The following standard calculated measures are available:
| 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). |
|---|---|
| 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. |
Original estimated hours Remaining estimated hours Hours spent with sub-tasks | Similar to Original estimated hours, Remaining estimated hours, Hours spent measures but include also estimated and actual hours of sub-tasks of selected issues. |
Properties
Properties are calculated measures retrieving 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 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 next-gen 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. |
| Assignee | Current assignee user for issues. 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. |
| Issue Type | Current issue type. For next-gen projects, issue type value is a combination of issue type and project key, like "Story (DEMO)". flex.bi 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 next-gen and standard projects. |
| Priority | Current issue priority. |
| Status | Current issue status. This dimension has a secondary hierarchy that aggregates members into Status Category. For next-gen projects, issue status value is a combination of status and project key, like "In Progress (DEMO)". flex.bi 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 next-gen and standard projects. |
| Resolution | Current (last) resolution if present. |
| 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. |
| 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 corresponding measure value will be included for all corresponding user groups in the user group dimension. |
Age interval Resolution interval | Interval dimensions. Age interval dimension aggregates currently unresolved issues by their age from issue created date till now; resolved issues are included in the (none) member of this dimension. Resolution interval aggregates currently resolved issues by resolution days; unresolved issues are included in the (none) member of this dimension. Intervals for those dimensions can be changed by report users based on their flex.bi user roles. |
Calculated members in Time dimension
When you create a new flex.bi account and import data there will be some predefined calculated members created in the Time dimension.
These calculated Time membres 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 |
flex.bi 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.