Jira Software custom fields import
If you use Jira Software (the former Jira Agile add-on) then the following additional custom field types are available in the Jira import custom fields selection:
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:
|Issue Flag is available for import as a property and a dimension. The value Impediment is used for flagged issues and (none) for not flagged. You can also import changes of this field to track when the isssues were flagged.|
|Rank||Rank could be imported only as a property, to show the issue current rank in the backlog.|
Sprint dimension contains sprints grouped by boards.
Property Issue Sprint shows issue current sprint value:
When Sprint is imported as a dimension, a bunch of measures are created to analyze sprint scope (based on Story Points if imported or issue counts). Using eazyBI standard measures with Sprint dimension, take into the account how they are counted to sprints!
|Story Points||Story points assigned to the issue, 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.|
Story Points total measures
When Story Points are imported as a measure, a set of total measures are created, similarly to other numeric custom fields.
Story Points created, Story Points resolved, Story Points due to get total story points from, respectively, all issues, resolved issues or unresolved issues. Story Points with due date counts story points from issues with due date. If closing statuses are defined in the account, then Story Points closed measure is also created to get total story points from closed issues. When value changes are imported as well for the Story points field, then Story Points changes is available.
Additionally there are hidden measures that shows total count of issues that have value for Story Points: Issues with Story points created, Issues with Story Points resolved, Issues with Story Points due.
All 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. Therefore, for sprint scope analyzis, use specifically designed measures (read about them in the next section "Sprint scope measures")
Sprint scope measures
Importing Sprint as a dimension, the additional set of measures designed for Sprint scope analyzis is created (find them in Analyze tab, Measures / Calculated members / Agile). To get the complete set of sprint scope change measures, you must import Issue change history. Also, if your Sprint scope is evaluated in story points, then import Story Points custom field as a measure with value changes.
Sprint start date
Sprint end date
Sprint complete date
Sprint start, end (planned) and completion dates are sprint properties. You can use them if you put sprints on pages or rows and then select these measures on columns to show particular dates.
Sprint goal is a sprint property as well and is available only in Jira Cloud.
|Sprint closed?||Sprint property that shows 'No' if a sprint is open and 'Yes' if closed.|
|Time within Sprint|
Measure that shows if the selected time period is within a sprint time period (from the sprint start date to the planned sprint end date). 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.
Sprint Story Points committed
Total of Story Points 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 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.
Sprint Story Points added
|Total of Story Points for issues which have been moved to (added) or from (removed) a selected sprint while the sprint was active. Can be used with the Time dimension at the Day level to see sprint scope changes.|
Sprint Story Points removed
Sprint Story Points change
|Total of Story Points changed for issues in a selected sprint while the sprint was active. Can be used with the Time dimension.|
Sprint Story Points at closing
Total of Story Points from sprint issues at the moment when the sprint was closed.
Sprint Story Points completed
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.
Sprint Story Points not completed
|Total of Story Points from issues that were in the sprint when the sprint was closed and were not completed.|
Sprint commitment changes
|Difference between the total of Story Points at the end of a sprint and Story Points at the start of the Sprint.|
Sprint issues committed
|Count of issues assigned to a selected sprint at the moment when the sprint was started.|
Sprint issues added
|Count of issues which have been moved to or from a selected sprint while the sprint was active. Can be used with the Time dimension.|
Sprint issues removed
Sprint issues at closing
|Count of sprint issues at the moment when the sprint was closed.|
Sprint issues completed
|Count of sprint completed issues at the moment when the sprint was closed. Issue is treated as completed if it was in one of the status category Done statuses at the sprint completion moment. The board configuration (a column mapping to statuses) is not taken into account for this measure.|
|Sprint issues not completed||Count of not completed sprint issues at the moment when the sprint was completed.|
|Sprint remaining estimated hours added||Total of remaining estimated hours for issues which have been moved to or from a selected sprint. Used with Time dimension, shows the number of Story points added or removed during a selected time period.|
|Sprint remaining estimated hours removed|
|Story Points history||Historical total of Story Points of issues in selected sprint. Used with Time dimension, shows the number of Story points at the end of a selected time period.|
|Cumulative Story Points resolved||Cumulative sum by Time dimension of Story Points resolved. Used with the Time dimension Day level, it shows up the burn-up of resolved story points.|
|Story Points remaining||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.|
Sprint Story Points remaining trend
Shows a trend for remaining story points. Used with the Time dimension Day level, shows the the burn-down trend.
Sprint Story Points guideline
|Sprint Story Points guideline shows ideal Story Points resolution guideline in working days for a selected sprint. Can be used with the Time dimension at the Day level.|
Running velocity for 5 closed sprints
|Calculates the average of resolved Story Points for the current sprint and 4 previous closed Sprints within a selected Project across all boards. You can create additional running velocity calculations using this as an example.|
All Closed Sprints
Calculated member in the Sprint dimension. It aggregates all closed sprints across all boards ordered by sprint start dates.
Other measures used with Sprints
Besides specifically designed Sprint scope measures, you may use other eazyBI measures together with Sprint. Then consider behaviour of the measures when they are used in the report (or in calculated measures) together with Sprint dimension:
- almost all basic (non-historical) measures counts issues against the issue current sprint.
- all historical measures (transitions) takes into account both, status and sprint historical values for the issue at the selected time period.
In the following table, there are more detailed description how most popular metrics work with Sprint dimension.
Issues created, Issues due, Issues closed, Issues resolved
<Custom field> created / due / closed / resolved
Measures Issues created (and all similar) shows how many issues (all, unresolved, closed accordingly to the measure) are currently assigned to the sprint. The same is true for total values from numerical custom measures: they calculates the totals from issues currently assigned to the sprint.
If the sprint has been completed, then only issues resolved during that sprint would still be counted to the sprint. And vica versa: if issue was not resolved during the sprint, even if it was in that sprint, it won't be counted to.
|Original estimated hours||Original estimated hours are counted only against the issue current sprint.|
Hours spent shows logged hours during a selected sprint.
Hours should be logged in the following period of a sprint to consider them as logged during the sprint (exact datetime is taken into account):
eazyBI looks for issue work log entries with "Date started" within the described time period and then sums up all time spent from those work logs.
For subtasks, the time period is calculated based on their parent issue data.
<Custom field> history
Issue history counts issues assigned to a sprint at the end of the selected time period. <Custom field> history counts total of the custom field value from the sprint issues at the end of the selected time period.
Those measure uses issue change history data.
If you selected the Import sample reports option, then additional sample reports are created in the Samples Jira Software folder. Please try these reports to see which measures would be useful for your specific needs. If you would like to customize some report then save it and change the name (as the default sample reports are overwritten during each Jira import).
Additional Sprint dimensions
The following additional hidden dimensions are created when Sprint and Issue change history is imported. They are used in calculated measure formulas to track count of issues and totals of Story Points when a sprint status is changed.
Sprint Status dimension with values:
|Issue Sprint Status Change|
Shows Issue and Sprint status transitions: