...
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.
...
| Section | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||
| ||||||||||||||||
| Section | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||
| ||||||||||||||||||
| Section | |||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||
| |||||||||||||||||||
...
| 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. |
...
There are three basic dimensions that constitute a hierarchy: Epic --> Issues --> Subtask.
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:
...
...
| 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.
| Section | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
|
...
| 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). |
...
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.
...
| DIMENSIONS | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Epics | Issues | Subtaks | Versions | Sprints | Story Points | Epic Status | Worklogs | Transitions | Links | Labels | Components | Comments | {Custom Field X} | |||||||
| 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. Custom Metrics.
You can create your own metrics through the integrated MDX editor. In this way you can adapt Analytics to your needs.
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 | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||
|
4. References
[2] Analysis Services Language Reference
[4] ISO 3166-2[3] Analysis Services Language Reference