...
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. |
|---|
Issu
|
| 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. |
|---|
Subtask| Subtasks | Corresponds to the subtasks of the board issues. |
|---|
| Attributes |
|---|
Issue | Subtask Key | Key + Summary of the |
|---|
issue issue | subtask is in the backlog. |
Issu Issue Issue Issue Issue Issue | Subtask estimated. Amount of time you believe is required to solve the |
issueIssue Issue | Subtask remaining. Amount of time you believe is required to solve the |
issue | subtask in its current state. |
Issue
|
| Subtask Project | Project to which the |
|---|
issue Issue Issue typeIssue
|
| Subtask Status Category | Status category of the |
|---|
issueIssue Issue Issue Issue priorityIssue ResolutionIssue Issue
|
| Subtask Time Created | Create date of the |
|---|
issue| subtask. | The date is separated in year, quarter, month, and day. |
Issue | Subtask Time Updated | Update date of the |
|---|
issue| subtask. | The date is separated in year, quarter, month, and day. |
Issue | Subtask Time Due | Due date of the |
|---|
issue| subtask. | The date is separated in year, quarter, month, and day. |
Issue | Subtask Time Resolved | Resolution date of the |
|---|
issue| subtask. | The date is separated in year, quarter, month, and day. |
2.2.2. Custom Field Dimensions.
...