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

Warning |
---|
|
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. |
---|
...
Section |
---|
|
Column |
---|
|
Dimension |
---|
Links | Corresponds to the linked issues of the JQL issues. |
---|
Attributes |
---|
Linked Issue TypeKey | Key + summary of the issues linked to JQL issues. |
---|
Link Type | Type of link. |
---|
|
Column |
---|
| 
|
|
...
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. |
---|
|
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 |
---|
|
Column |
---|
|
Number Field |
---|
Attributes |
---|
<Custom Field Name> | Value of the custom. |
---|
|
Column |
---|
| 
|
|
Section |
---|
|
Column |
---|
|
Select List (Cascading) |
---|
Attributes |
---|
<Custom Field Name> Option | Custom field select option. |
---|
<Custom Field Name> SubOption | Suboption within the custom field option. |
---|
|
Column |
---|
| 
|
|
Section |
---|
|
Column |
---|
|
Date Picker |
---|
Attributes |
---|
<Custom Field Name> | Date included in the custom field. | The date is seperated in year, quarter, month and day. |
---|
|
Column |
---|
| 
|
|
...
Section |
---|
|
Column |
---|
|
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 |
---|
| 
|
|
Anchor |
---|
| 1.2. Measures. |
---|
| 1.2. Measures. |
---|
|
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. |
---|
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. |
---|
Count Different Components | Count the components without repetition. | Differences between the metrics: 
|
---|
Count Total Components | Count the components with repetition. |
---|
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.
...
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. |
---|
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.
...
Section |
---|
|
Column |
---|
| Data in JIRA: 
|
Column |
---|
| 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 |
---|
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. |
---|
2.2.2. Custom Field Dimensions.
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 |
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. |
---|
Section |
---|
|
Column |
---|
|
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. |
---|
|
Column |
---|
| Image Added
|
|
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.
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 |
---|
|
Column |
---|
| 1. Calculate the story points of each epic.
Image Added
|
Column |
---|
| 2. Add an calculated percentage metric.
Image Added
|
Column |
---|
| 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