Jira Software custom fields

With eazyBI version 6.0 added support for Sprint planned and actual dates introduced with Jira version 8.7. We updated formulas for predefined measures and members and calculations in Demo account. Verify custom formulas and imported formulas from our demo account to reflect those changes.



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

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 listedEpic 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. Epic Name could be used as a name for the members of Epic Link dimension instead of the default "key+short summary". To use Epic Name as the dimension member name, use advanced settings.
  3. Issue Epic Status: for epic issues, the issue Epic Status.

Flagged

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.
RankRank could be imported only as a property, to show the issue current rank in the backlog.

Sprint

Sprint dimension contains sprints grouped by boards.

Property Issue Sprint shows issue current sprint value:

  • Sprint from the Jira field "Active sprint",
  • Sprint in which the issue was completed (resolved); usually, the last from "Completed sprints" field.
  • (none) for issues that were not completed in neither of "Completed sprints" and currently are not included in any active sprint.

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 PointsStory 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 estimated

Story points assigned to the issue in the next-gen 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 next-gen project is detected in the project list.


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 a 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 show the total count of issues that have value for Story Points: Issues with Story points created, Issues with Story Points resolvedIssues 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 analysis, 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 analysis 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 UPDATED

Sprint start date reflects planned start date of the sprint.

Meaning of Sprint start date changes with version 6.0. Verify custom formulas and address Sprint status property or Sprint actual start date to retrieve Active Sprints.

Sprint end date Sprint end date reflects planned end date of the sprint. 

Sprint actual start date NEW

Sprint actual start date reflects date and time when sprint was started. Sprint measures representing committed scope takes into accounts this date.

Sprint actual end date UPDATED

Sprint actual end date reflects date and time when sprint was completed. 

Measure Sprint actual end date works instead of the previous measure Sprint complete date. Verify custom formulas and address the new name of this measure. Sprint property name did not change.

Sprint goalSprint goal is a sprint property
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 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.

Sprint Story Points committed  UPDATED

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.

Since eazyBI version 6.0 formula works for any board and other sprint selection. The behaviour change might require some changes in custom calculations for guidelines or predictions. Verify your formulas and address committed points in tuple with time default member.

Sprint Story Points added

Total of Story Points for issues that 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 which 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  UPDATED

Count of issues assigned to a selected sprint at the moment when the sprint was started. 

Since eazyBI version 6.0 formula works for any board and other sprint selection. The behaviour change might require some changes in custom calculations for guidelines or predictions. Verify your formulas and address committed issues in tuple with time default member.


Sprint issues added 

Count of issues which have been moved to or from a selected sprint while the sprint was active. It 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 completedCount of not completed sprint issues at the moment when the sprint was completed.
Sprint remaining estimated hours addedTotal of remaining estimated hours for all issues that have been added to/removed from (at any moment) the selected sprint. Remaining estimated hours are captured at the moment when the issue was added to/removed from the sprint.
Sprint remaining estimated hours removed
Story Points historyHistorical 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.
Cumulative Story Points resolvedCumulative 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 remainingThe 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.

Linear trend Story Points remaining
UPDATED

Shows a trend for remaining story points using default calculation Add standard calculations - Linear trend

Previous predefined measure Sprint Story Points remaining trend is moved to User defined measures if used in other reports

Sprint Story Points guideline

Sprint Story Points guideline shows ideal Story Points resolution guidelines in working days for a selected sprint. It 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.


Measures for next-gen projects

When you have next-gen projects, make sure to select field Story points estimate for data import. During data import, eazyBI will create a set of story points total and Sprint scope measures.

When Story points estimate are imported as a measure, a set of total measures are created, similar to other numeric custom fields. Those measures are available in the predefined measurement section Agile (next-gen). Note there is still section Agile that holds common metrics and properties for next-gen and other projects, like Sprint properties and measures related to issue count.

Story points estimate created, Story points estimate resolved, Story points estimate due to get total story points from, respectively, all issues, resolved issues or unresolved issues. Story points estimate with due date counts story points from issues with a due date. 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.

In addition, you may import the following Story point estimate measures:

Story points estimate closed

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 represent the current issue story point value and could be used to analyze data by issue current statuses, priorities, projects, etc.

Make sure to select closing statuses of all selected next-gen projects.

Story points estimate changes

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.

Story point estimate history

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.

Cumulative Story point estimate resolvedCumulative sum by Time dimension of Story point estimate resolved. Used with the Time dimension Day level, it shows up the burn-up of resolved story points.
Story point estimate remainingThe remaining story points by the Time dimension are calculated as the total Story point estimate scope (Story point estimate history measure) minus Cumulative Story point estimate resolved measure. Used with Time dimension, shows remaining Story points at the end of a selected time period.

For sprint scope analysis, use specifically designed measures in the table below:

Sprint Story point estimate committed

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 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 point estimate added

Total of Story point estimate for issues that have been moved to (added) or from (removed) a selected sprint while the sprint was active. It can be used with the Time dimension at the Day level to see sprint scope changes. 

Sprint Story point estimate removed

Sprint Story point estimate change

Total of Story point estimate changed for issues in a selected sprint while the sprint was active. It can be used with the Time dimension.

Sprint Story point estimate at closing

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

Sprint Story point estimate completed

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 Story point estimate not completed

Total of Story point estimate from issues that were in the sprint, when the sprint was closed, and which were not completed.
Sprint Story point estimate commitment changesDifference between the total of Story point estimate at the end of a sprint and Story point estimate at the start of the Sprint.
Sprint Story point estimate remaining trendShows a trend for remaining story points. Used with the Time dimension Day level, it shows the burn-down trend.
Sprint Story point estimate guidelineShows ideal Story point estimate resolution guidelines in working days for a selected sprint. It can be used with the Time dimension at the Day level.
Running Story point estimate velocity for 5 closed sprintsCalculates the average of resolved Story point estimate 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.


Other measures used with Sprints

Besides specifically designed Sprint scope measures, you may use other eazyBI measures together with Sprint. Then consider the behavior of the measures when they are used in the report (or in calculated measures) together with Sprint dimension:

  • almost all basic (non-historical) measures count 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 a more detailed description of how the most popular metrics work with the 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 calculate 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 vice versa: if the issue was not resolved during the sprint, even if it was in that sprint, it won't be counted against.

Original estimated hoursOriginal estimated hours are counted only against the issue's current sprint.
Hours spent

Hours spent show 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):

  • from the sprint start date or the date when the issue was added to the sprint if it happened after the sprint was started;
  • to the date when the issue was removed from sprint, or sprint completion date (if the issue was not resolved during the sprint); for issues resolved during the sprint, all hours logged after the sprint is closed also are counted.

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.

Issues history

<Custom field> history

Issue history counts issues assigned to a sprint at the end of the selected time period. <Custom field> history counts a total of the custom field value from the sprint issues at the end of the selected time period.

Those measures use issue change history data.


Sample reports

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
(hidden)

Sprint Status dimension with values:

(none)Backlog
FuturePlanned future sprint
ActiveActive sprint
ClosedClosed sprint
Issue Sprint Status Change
(hidden) 

Shows Issue and Sprint status transitions:

(none) => FutureAn issue was added to a future sprint
(none) => ActiveAn issue was added to an active sprint
Future => (none)An issue was removed from a future sprint
Active => (none)An issue was removed from an active sprint
Future => ActiveA sprint was started and an issue was committed to it
Active => ClosedAn issue was in a sprint when it was closed
Closed => (none)An issue was moved to the backlog after a sprint was closed