Jira Software custom fields

eazyBI for Jira

Epic Link custom field import creates additional Epic Link dimension where all the epics having at least one linked issue imported into this account are listed. Epic Link dimension can be used to get totals of issues or story points per selected epics, data from sub-tasks are not included in those totals then.

In addition, in the Issue dimension, Epic hierarchy is created (you can import Epic Link only as a property, the hierarchy still will be build). Using this hierarchy, totals of issues per selected epic, including from the issue sub-tasks, are calculated in the report.

Importing Epic Link as a property, three issue properties are created:

1. Issue Epic Link: issue epic link key.
2. Issue Epic Name: for epic issues, the issue Epic Name. 
3. Issue Epic Status: for epic issues, the issue Epic Status.

This field is hidden from the custom field list.

Epic name is a field only for epic issues and it is automatically imported as issue property "Issue Epic Name" when custom field "Epic Link" is selected for data import.

However, you may import Epic Name also as a separate dimension using advanced settings. Please follow the instructions here on how to add advanced settings. When settings are in place, import data (the field will be hidden from the custom field list, therefore is no need to select it separately).

Sprint dimension contains sprints grouped by boards (default hierarchy) or by Sprint status (Status hierarchy). When Sprint is imported as a dimension, a set of measures is created to analyze sprint scope (based on Story Points if imported or issue counts). Using eazyBI standard measures with Sprint dimension, take into account how they are counted to the sprints!

Properties Issue Sprint and Issue Sprint Status show a name and a status of issue current sprint. An issue always has only one current sprint and it could be one of the following:

• Sprint from the Jira field "Active sprint" (the ongoing sprint the issue is added to),
• Sprint in which the issue was resolved (resolution date within the sprint); usually, the last from the "Completed sprints" field.
• (none) for issues that were not resolved (set resolution date) in neither of "Completed sprints" and currently are not included in any active or future sprints.

Property Issue Sprints show a comma-separated list of Sprint names that are assigned to an issue field "Sprint" in Jira.

There is an option to create custom hierarchies in the Sprint dimension with the Add custom hierarchy. It is possible to create a hierarchy based on custom Sprint properties imported with additional data import.

Story points assigned to the issue in the team-managed project, imported as a measure, also value change information could be imported. As a result, a set of measures are created based on Story points information, as well as in a combination with Sprint information.

This option is available and marked when the team-managed project is detected in the project list.

Total story points from all created issues, resolved issues, or unresolved issues; see measure description Jira Core measures and dimensions.

Those measures are based on the current issue story point value and could be used to analyze data by issue current statuses, priorities, projects, etc.

You can also break down those metrics by Sprints but take into account that all those values would be counted by the issue current sprint, thus, recommended to use only for data analyze in ongoing (active) sprints or for resolved issues only. For Story points analyze in completed sprints, consider using sprint scope measures.

Hidden measures that could be used in the calculated measures.

Total count of created, resolved, or unresolved issues that have value for Story Points: 

Total story points from issues with a due date in the selected period.  This measure is also based on the current issue story point value.

Historical total of Story Points of issues in the selected sprint. Used with Time dimension, shows the number of Story points at the end of a selected time period.

This measure is based on issue change history.

Story points increased or decreased compared to the previous period. It is calculated as a sum of hidden measures Story Points added and Story Points removed.

This measure is based on issue change history.

Hidden measure that could be used in the calculated measures.

Total of story points increased for all recorded activities (sprint status change, status transition, change of assignee, etc.) during the selected period. It is recommended to use this measure together with other dimensions that would describe the activity.

This measure is based on issue change history.

Hidden measure that could be used in the calculated measures.

Total of story points decreased for all recorded activities (sprint status change, status transition, change of assignee, etc.) during the selected period. It is recommended to use this measure together with other dimensions that would describe the activity.

This measure is based on issue change history.

Measure that shows if the selected time period is within a sprint time period (from the sprint actual start date to the planned sprint end date or today if sprint was not completed in time for active sprint, or till actual end date for completed sprints). Measure shows value 1 if the current Time dimension period (typically, days on rows) is within a selected Sprint (typically on pages). This measure can be used to filter dates just for the selected sprint in burn-down and burn-up charts.

Total of Story Points for issues that have been moved to (added) or from (removed) a selected sprint while the sprint was active. eazyBI captures the story point value at the moment of movement.

Measure can be used with the Time dimension at the Day level to see sprint scope changes.

Total of Story Points from sprint issues at the moment when the sprint was closed.

Total of Story Points from sprint issues that were completed when the sprint was closed.

Issue story points are treated as completed if the issue was in one of the status category Done statuses at sprint completion moment. The board configuration (a column mapping to statuses) is not taken into account for this measure.

The remaining story points by the Time dimension are calculated as the total Story Points scope (Story Points history measure) minus Cumulative Story Points resolved measure. Used with Time dimension, shows remaining Story points at the end of a selected time period.

Use measure Sprint Story Points remaining to view Story Points from not completed issues at the end of Sprint.

If closing statuses are defined in the account, then Story points estimate closed measure is also created to get total story points from closed issues. This measure represents the current issue story point value and could be used to analyze data by issue current statuses, priorities, projects, etc.

Make sure to select the closing statuses of all selected team-managed projects.

Story point estimate value change (increased or decreased value compared to the previous period) in the selected Time dimension period.

Make sure to select value change for field Story point estimate in import options to get this measure.

Historical total of Story point estimate of issues in the selected sprint. Used with Time dimension, shows the number of Story point estimate at the end of a selected time period.

Make sure to select value change for field Story point estimate in import options to get this measure.

Total of Story point estimate from issues assigned to a selected sprint at the time when the sprint was started. Story points are counted from issues, whether there were completed or not at the start of the sprint. Actions that happened after the sprint was started (issues added, removed, story point changes, etc) are not taken into account when the committed points are calculated.

The measure is calculated only in a single sprint level; for totals, a calculated measure should be created.

Total of Story point estimate from sprint issues at the moment when the sprint was closed.

Total of Story point estimate from sprint issues that were completed when the sprint was closed.

Issue story points are treated as completed if the issue was in one of the status category Done statuses at sprint completion moment. The board configuration (a column mapping to statuses) is not taken into account for this measure.

Sprint Status dimension with values:

Shows Issue and Sprint status transitions: