Table of Contents

style	none

...

1. Jira Core Cube.

The JIRA Core cube works on a JQL and is launched from the issue navigator. All the calculations made will refer to the JQL issues.

...

For example, the versions of a given issue will be those that appear only in the issue. Possible versions that appear in your subtasks will not be counted as versions of the issue.

1.1. Dimensions/Attributes.

The JIRA Core cube provides 8 basic dimensions to extract information from issues. In addition to these dimensions, a new dimension will be added for each customfield that you want to include in the cube.

1.1.1. Basic Dimenions.

Dimension
Issue	Corresponds to the JQL issues.
Attributes
Issue Key		Key + Summary of the issue.
Assignee		Issue assigned.
Reporter		Issue creator.
Estimated		Issue estimated. Amount of time you believe is required to solve the issue.
Remaining		Issue remaining. Amount of time you believe is required to solve the issue in its current state.
Project		Project to which the issue belongs.
Type		Issue type.
Status Category		Status category of the issue.
Status		Issue status.
Priority		Issue priority.
Resolution		Issue resolution.
Time Created		Create date of the issue.	The date is separated in year, quarter, month, and day.
Time Updated		Update date of the issue.	The date is separated in year, quarter, month, and day.
Time Due		Due date of the issue.	The date is separated in year, quarter, month, and day.
Time Resolved		Resolution date of the issue.	The date is separated in year, quarter, month, and day.

...

Dimension
Comments	corresponds to the comments of the JQL issues.
Attributes
Author	Author of the comment.
Updater	Last user who updated the comment.
Time Created	Create date of the comment.	The date is separated in year, quarter, month, day, hour and minute.
Time Updated	Last update date of the comment.	The date is separated in year, quarter, month, day, hour and minute.

Anchor
1.1.2. Custom Field Dimensions.
1.1.2. Custom Field Dimensions.

Users can add custom fields to the JIRA Core cube to extract information about them. These custom fields will be added as dimensions in the cube.

...

Section

border	true

Column

width	70%

Version Picker (multiple versions)
Attributes
<Custom Field Name>	Versions of the custom field.
Archived Version	If the version has been archived or not.
Released Version	If the version has been released or not.
Time Release	Release date of the version.
Time Start	Start date of the version.

Column

width	30%

1.2. Measures.

MEASURES
Count Issues	Count the issues.
Sum Estimated Time	Sum the estimated time.
Sum Remaining Time	Sum the remaining time.
Count Different Versions	Count the versions without repetition..	Differences between the metrics:
Count Total Versions	Count the versions with repetition.	Differences between the metrics:
Count Worklogs	Count the worklogs.
Sum Time Spent	Sum worklog time.
Count Different Labels	Count the labels without repetition.	Differences between the metrics:
Count Total Labels	Count the labels with repetition.	Differences between the metrics:
Count Different Components	Count the components without repetition.	Differences between the metrics:
Count Total Components	Count the components with repetition.	Differences between the metrics:
Count Transitions	Count the transitions.
Sum Time in Status From	Sum time in a status.
Count Num. Links	Count the links.	Differences between the metrics:
Count Linked Issues	Count the linked issues.
Count Link Types	Count the types of links.
Count Comments	Count the number of comments.

...

MEASURES FOR CUSTOM FIELD NUMBER
{Min Custom Field Number}	Minimum value of the numerical custom field.
{Max Custom Field Number}	Maximum value of the numerical custom field.
{Sum Custom Field Number}	Sum value of the numerical custom field.
{Avg Custom Field Number}	Average value of the numerical custom field.

1.3. Dimensions/Measures matrix.

The matrix specifies the dimensions on which a metric can be applied.

...

		DIMENSIONS
		Comments	Component	Issue	Label	Links	Transitions	Version	Worklog	{Custom Field X}
Measures	Count Issues
	Sum Estimated Time
	Sum Remaining Time
	Count Different Versions
	Count Total Versions
	Count Worklogs
	Sum Time Spent
	Count Different Labels
	Count Total Labels
	Count Different Components
	Count Total Components
	Count Transitions
	Sum Time in Status From
	Count Num. Links
	Count Linked Issues
	Count Link Types
	Count Comments
	{Min Custom Field Number}
	{Max Custom Field Number}
	{Sum Custom Field Number}
	{Avg Custom Field Number}

2. Jira Software Cube.

The JIRA Software cube works on a board (Kanban or Scrum) and is launched from a board. All calculations made will refer to the board issues.

...

Section

border	true

Column

width	60%

Data in JIRA:

Column

width	40%

Analytics:

2.1. Dimensions/Attributes.

The JIRA Core cube provides 8 basic dimensions to extract information from issues. In addition to these dimensions, a new dimension will be added for each customfield that you want to include in the cube.

2.1.1. Basic Dimensions.

Dimension
Epics	Corresponds to the epics of the board.
Attributes
Epic Key	Key + Summary of the epic.
Epic Project	Project to which the epic belongs.
Epic Assignee	Epic assigned.
Epic Reporter	Epic creator.
Epic Estimated	Epic estimated. Amount of time you believe is required to solve the epic.
Epic Remaining	Epic remaining. Amount of time you believe is required to solve the epic in its current state.
Epic Status Category	Status category of the epic.
Epic Status	Epic status.
Epic Priority	Epic priority.
Epic Resolution	Epic resolution.
Epic Created	Create date of the epic.	The date is separated in year, quarter, month, and day.
Epic Updated	Update date of the epic.	The date is separated in year, quarter, month, and day.
Epic Due	Due date of the epic.	The date is separated in year, quarter, month, and day.
Epic Resolved	Resolution date of the epic.	The date is separated in year, quarter, month, and day.

...

Dimension
Sprints	Corresponds to the board sprints.
Attributes
Sprint Name	Name of the sprint.
Sprint State	State of the sprint (Active, Closed, Future)
Time Start Sprint	Start date of the sprint.	The date is separated in year, quarter, month, day, hour and minute.
Time Complete Sprint	Complete date of the sprint.	The date is separated in year, quarter, month, day, hour and minute.
Time End Sprint	End date of the sprint.	The date is separated in year, quarter, month, day, hour and minute.

Dimension
Story Points	Corresponds to the story points of the Histories.
Attributes
Story Point Value	Value of the story point.

Dimension
Epic Status	Corresponds to the state of the epic. In JIRA, it is presented in a custom field.
Attributes
Epic Status Value	Current state of the epic (To Do, In Progress, Done).

Dimension
Worklogs	Corresponds to the worklogs of the board issues.
Attributes
Logger	Author of the worklog.
Time Created	Create date of the worklog.	The date is separated in year, quarter, month, and day.
Time Start	Date when you started the unit of work.	The date is separated in year, quarter, month, and day.

...

Dimension
Comments	corresponds to the comments of the board issues.
Attributes
Author	Author of the comment.
Updater	Last user who updated the comment.
Time Created	Create date of the comment.	The date is separated in year, quarter, month, day, hour and minute.
Time Updated	Last update date of the comment.	The date is separated in year, quarter, month, day, hour and minute.

2.2.2. Custom Field Dimensions.

The custom fields dimensions work the same as for the JIRA Core cube. Users can add custom fields to the JIRA Core cube to extract information about them.

2.2. Measures.

2.3. Dimensions/Measures matrix.

The matrix specifies the dimensions on which a metric can be applied.

...

		DIMENSIONS
		Epics	Issues	Subtaks	Versions	Sprints	Story Points	Epic Status	Worklogs	Transitions	Links	Labels	Components	Comments	{Custom Field X}
Measures	Count Epics
	Count Issues
	Count Subtask
	Sum Estimated Time
	Sum Remaining Time
	Count Sprints
	Count Different Versions
	Count Total Versions
	Count Worklogs
	Sum Time Spent
	Count Transitions
	Sum Time in Status From
	Min Story Points
	Max Story Points
	Sum Story Points
	Avg Stroy Points
	Count Num. Links
	Count Linked Issues
	Count Link Types
	Count Different Labels
	Count Total Labels
	Count Different Components
	Count Total Components
	Count Comments
	{Min Custom Field Number}
	{Max Custom Field Number}
	{Sum Custom Field Number}
	{Avg Custom Field Number}

3. References

[1] Saiku Documentation

[2] ISO 3166-2

...

Version	Old Version 91	New Version 92
Changes made by	David Ortiz	David Ortiz
Saved on	May 17, 2018	May 17, 2018

Content Comparison

Versions Compared

Key

1. Jira Core Cube.

1.1. Dimensions/Attributes.

1.1.1. Basic Dimenions.

Anchor1.1.2. Custom Field Dimensions.1.1.2. Custom Field Dimensions.

1.2. Measures.

1.3. Dimensions/Measures matrix.

2. Jira Software Cube.

2.1. Dimensions/Attributes.

2.1.1. Basic Dimensions.

2.2.2. Custom Field Dimensions.

2.2. Measures.

2.3. Dimensions/Measures matrix.

3. References

Anchor
1.1.2. Custom Field Dimensions.
1.1.2. Custom Field Dimensions.