Gallery

include	image2018-5-17_10-8-47.png, image2018-5-17_10-11-58.png, image2018-5-17_10-6-13.png, image2018-5-17_11-13-51.png, image2018-5-17_11-16-12.png, image2018-5-17_11-5-15.png
title	The power of Analytics

Section

Column

width	33%

Column

width	33%

Column

width	33%

...

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.Image RemovedJQL issues.

Image Added

Warning

title	JQL is required

JQL is required to load the JIRA Core cube.

The JIRA Core cube works separately with the issues, and extracts information from them without taking into account hierarchies.

...

Section

border	true

Column

width	70%

Number Field
Attributes
<Custom Field Name>	Value of the custom.

Column

width	30%

Section

border	true

Column

width	70%

Select List (Cascading)
Attributes
<Custom Field Name> Option	Custom field select option.
<Custom Field Name> SubOption	Suboption within the custom field option.

Column

width	30%

Section

border	true

Column

width	70%

Date Picker
Attributes
<Custom Field Name>	Date included in the custom field.	The date is seperated in year, quarter, month and day.

Column

width	30%

...

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.

...

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.

Image Removed

There are three basic dimensions that constitute a hierarchy:

Epic --> Issues --> Subtask. will refer to the board issues.

Image Added

There are three basic dimensions that constitute a hierarchy: Epic --> Issues --> Subtask.

Hierarchy
Epic			Epics of the board.	Issue type Epic.
Image Added	Issue		Issues included in the epic	Standard issue types, except epic type.
	Image Added	Subtask	Subtasks of the issues included in the epics	Subtask issue types.

Any calculation on one of these dimensions will include the data of its descendants in the hierarchy.

...

Value of the story point

Dimension
Story Points	Corresponds to the story points of the Histories.
Attributes
Story Point Value	Value	Value of the story point. As in JIRA Software, the history points of the epics will not be taken into account for the calculations.

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).

...

In addition, the JIRA Software cube adds some new metrics:adds some new metrics:

MEASURES
Count Epics	Count epics.
Count Subtask	Count subtask.
Count Sprints	Count sprints.
Min Story Points	Minimum value of history points.
Max Story Points	Maximum value of history points.
Sum Story Points	Sum value of history points.
Avg Story Points	Average value of history points.

2.3. Dimensions/Measures matrix.

...

Image Removed

		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 IssuesIssues	Image Added	Image Added	Image Added	Image Added	Image Added	Image Added	Image Added	Image Added	Image Added	Image Added	Image Added	Image Added	Image Added	Image Added
	Count Link Types	Image Added	Image Added	Image Added	Image Added	Image Added	Image Added	Image Added	Image Added	Image Added	Image Added	Image Added	Image Added	Image Added	Image Added
	Count Different Labels	Image Modified	Image Modified	Image Modified	Image Modified	Image Modified	Image Modified	Image Modified	Image Modified	Image Modified	Image Added	Image Modified	Image Modified	Image Modified
	Count Link TypesTotal Labels									Image Removed	Image Added
	Count Different LabelsComponents
	Count Total LabelsComponents
	Count Different ComponentsComments
	Count Total Components{Min Custom Field Number}
	Count Comments{Max Custom Field Number}
	{Min Sum Custom Field Number}
	{Max Avg Custom Field Number}
{Sum Custom Field Number}	Image Removed	Image Removed	Image Removed	Image Removed	Image Removed	Image Removed	Image Removed	Image Removed	Image Removed	Image Removed	Image Removed	Image Removed	Image Removed	Image Removed
{Avg Custom Field Number}	Image Removed	Image Removed	Image Removed	Image Removed	Image Removed	Image Removed	Image Removed	Image Removed	Image Removed	Image Removed	Image Removed	Image Removed	Image Removed	Image Removed

...

3. Custom Metrics.

You can create your own metrics through the integrated MDX editor. In this way you can adapt Analytics to your needs.

Image Added

3.1. Calculating Percentages.

You can easily calculate the percentages of your metrics through the integrated MDX editor.

For example, if you wanted to know the percentage of story points resolved for each epic.

Section

border	true

Column

width	33%

1. Calculate the story points of each epic.

Image Added

Column

width	33%

2. Add an calculated percentage metric.

Image Added

Column

width	33%

3. The calculated metric will be added to the available metrics.

Image Added

4. References

[1] Saiku Documentation

[2] Analysis Services Language Reference

[3] Saiku Chart Plus

[4] ISO 3166-2 [3] Analysis Services Language Reference

Version	Old Version 97	New Version Current
Changes made by	David Ortiz	David Ortiz
Saved on	May 17, 2018	May 21, 2018

Versions Compared

Key

2.3. Dimensions/Measures matrix.

3. Custom Metrics.

3.1. Calculating Percentages.

4. References

Content Comparison

Versions Compared

Key

2.3. Dimensions/Measures matrix.

3. Custom Metrics.

3.1. Calculating Percentages.

4. References