This section describes the functionality provided in the analytics cubes.

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.

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.

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
Version	Corresponds to the versions that appear in the JQL issues. If a version does not have issues, it will not appear in the queries.
Attributes
Name Version	Name of the vesion.
Type Version	Indicates whether a version appears in an issue such as 'Affects Version/s' or 'Fix Version/s'
Archived Version	If the version has been archived or not.
Released Version	If the version has been released or not.
Time Start	Start date of the version.	The date is separated in year, quarter, month, and day.
Time Release	Release date of the version.	The date is separated in year, quarter, month, and day.

Dimension
Worklog	Corresponds to the worklogs of the JQL 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
Label	Corresponds to the labels that appear in the JQL issues.
Attributes
Label	Label name.

Dimension
Component	Corresponds to the components that appear in the JQL issues.
Attributes
Component Name	Component name.
Component Lead	Responsible/leader of the component.

Dimension
Transitions	Corresponds to the transitions of the JQL issues.
Attributes
Status - From	State "from" of the transition.
Status - To	State "to" of the transition.
Performed by	Author of the transition.
Time Transition	Date on which the transition was made.	The date is separated in year, quarter, month, and day.

Dimension
Links	Corresponds to the linked issues of the JQL issues.
Attributes
Linked Issue Key	Key + summary of the issues linked to JQL issues.
Link Type	Type of link.

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.

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.

The name of the new dimension will be:

<custom field identifier> - <custom field name>

This nomenclature gives the possibility to include custom fields that have the same name.

The types of custom fields allowed are:

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

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

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

Date Time Picker
Attributes
<Custom Field Name>	Date and time included in the custom field.	The date is separated in year, quarter, month, day, hour and minute.

Labels
Attributes
<Custom Field Name>	Custom field labels.

Project Picker (single project)
Attributes
<Custom Field Name>	Project of the custom field.

User Picker (single user)
Attributes
<Custom Field Name>	User of the custom field.

User Picker (multiple users)
Attributes
<Custom Field Name>	Users of the custom field.

Group Picker (single group)
Attributes
<Custom Field Name>	Group of the custom field.

Group Picker (multiple groups)
Attributes
<Custom Field Name>	Groups of the custom field.

Version Picker (single version)
Attributes
<Custom Field Name>	Version 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.

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.

1.2. Measures.

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

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

Hierarchy
Epic			Epics of the board.	Issue type Epic.
	Issue		Issues included in the epic	Standard issue types, except epic type.
		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.

For example, the versions of an epic will be:

The versions of the epic itself.
Plus the versions of the issues included in the epic.
Plus the versions of the subtasks of the issues included in the epic.

Data in Jira:

Analytics:

Other example, the estimated time of an issue will be:

The time of the issue.
Plus the estimated times of the subtasks of the issue.

Data in JIRA:

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
Issues	Corresponds to the issues of the board. All board issues, except epics and subtasks.
Attributes
Issue Key		Key + Summary of the issue.
In Backlog		If the issue is in the backlog.
Issue Assignee		Issue assigned.
Issue Reporter		Issue creator.
Issue Estimated		Issue estimated. Amount of time you believe is required to solve the issue.
Issue Remaining		Issue remaining. Amount of time you believe is required to solve the issue in its current state.
Issue Project		Project to which the issue belongs.
Issue Type		Issue type.
Issue Status Category		Status category of the issue.
Issue Status		Issue status.
Issue Priority		Issue priority.
Issue Resolution		Issue resolution.
Issue Time Created		Create date of the issue.	The date is separated in year, quarter, month, and day.
Issue Time Updated		Update date of the issue.	The date is separated in year, quarter, month, and day.
Issue Time Due		Due date of the issue.	The date is separated in year, quarter, month, and day.
Issue Time Resolved		Resolution date of the issue.	The date is separated in year, quarter, month, and day.

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

Dimension
Versions	Corresponds to the versions that appear in the board issues. If a version does not have issues, it will not appear in the queries.
Attributes
Name Version	Name of the vesion.
Type Version	Indicates whether a version appears in an issue such as 'Affects Version/s' or 'Fix Version/s'
Project Version	Project of the version.
Archived Version	If the version has been archived or not.
Released Version	If the version has been released or not.
Time Start Version	Start date of the version.	The date is separated in year, quarter, month, and day.
Time Release Version	Release date of the version.	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. 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).

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
Transitions	Corresponds to the transitions of the board issues.
Attributes
Status - From	State "from" of the transition.
Status - To	State "to" of the transition.
Performed by	Author of the transition.
Time Transition	Date on which the transition was made.	The date is separated in year, quarter, month, and day.

Dimension
Links	Corresponds to the linked issues of the board issues.
Attributes
Linked Issue	Key + summary of the issues linked to board issues.
Link Type	Type of link.

Dimension
Labels	Corresponds to the labels that appear in the board issues.
Attributes
Label	Label name.

Dimension
Components	Corresponds to the components that appear in the board issues.
Attributes
Component Name	Component name.
Component Lead	Responsible/leader of the component.

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.

(View 1.1.2. Custom Field Dimensions)

2.2. Measures.

The JIRA Software cube uses the same metrics as the JIRA Core cube.

(View 1.2. Measures)

In addition, the JIRA Software cube 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.

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}