Time tracking measures
eazyBI for Jira
Available for eazyBI for Jira Cloud and since eazyBI version 6.6.
By default, eazyBI imports measures Hours spent and Original estimated hours as part of core measures. Those measures represent originally estimated time on issues and actually spent time on issues. While you can use those measures in many reports, they are hard to analyze side by side over time.
eazyBI allows importing additional measures to analyze spent time and originally estimated time by issue resolution and close dates. If you would like to extend time tracking measure analysis, we suggest enabling an import of the additional set of measures for time tracking. Go to import options, tab Additional options, and mark the option to import additional measures for Hours spent and Original estimated hours.
Measures
eazyBI creates a set of additional measures organized in the predefined measures section Time Tracking.
Original estimated hours | Total of original estimated hours. Used with the Time dimension, grouped by issue creation dates. Original estimated hours measures is available by default even when the Time tracking measures option isn't selected in import options. |
|---|---|
Original estimated hours resolved | Total of original estimated hours for the resolved issues. They are grouped by issue resolution date in the Time dimension. |
Original estimated hours closed | Total of original estimated hours for the closed issues. They are grouped by issue closed date in the Time dimension. |
Hours spent | Total of hours spent on issues matching the selected dimension members. On the Time dimension grouped by the start date specified in the worklog. The Logged by dimension can be used to see hours spent by individual users. You can Drill through the cell to get a list of all worklog entries constituting particular Hours spent total value, with additional information -user name, date, issue key, worklog comments, as well as logged hours for this entry. The list could be exported to a file. Hours spent measures is available by default even when the Time tracking measures option isn't selected in import options. If you use the Tempo app in Jira Cloud, please see how to enable worklog import. |
Hours spent resolved | Total of hours spent on resolved issues. They are grouped by issue resolution date in the Time dimension. |
Hours spent closed | Total of hours spent on closed issues. They are grouped by issue closed date on Time dimension. |
Original estimated hours accuracy % | Accuracy of estimated hours compared to the total time spent on resolved issues in the period. |
Average hours spent of resolved issues | Calculates average hours spent on resolved issues with logged time. They are grouped by issue resolution date in the Time dimension. |
Issues with Original estimated hours resolved | Count of resolved issues with original estimated hours. They are grouped by issue resolution date in the Time dimension. Hidden measure. |
Issues with Original estimated hours closed | Count of closed issues with original estimated hours. They are grouped by issue closed date in the Time dimension. Hidden measure. |
Issues with hours spent | Distinct count of issues that have any hours logged in the selected Time period. Hours spent measures is available by default even when the Time tracking measures option isn't selected in import options. |
Issues with hours spent resolved | Count of resolved issues with hours spent. They are grouped by issue resolution date in the Time dimension. Hidden measure. |
Issues with hours spent closed | Count of closed issues with hours spent. They are grouped by issue closed date in the Time dimension. Hidden measure. |
Remaining estimated hours | Total of current remaining estimated hours. Used with the Time dimension, grouped by issue due dates for unresolved issues and by resolution dates for resolved issues. Remaining estimated hours measures is available by default even when the Time tracking measures option isn't selected in import options. |
Original estimated hours with sub-tasksRemaining estimated hours with sub-tasksHours spent with sub-tasks | Retrieve Original estimated hours, Remaining estimated hours, and Hours spent values for parent-level issues, including their sub-task issue values; for sub-task level issues, the value is always zero. Use those measures in reports and calculations in case you need to apply filters on parent issues only; otherwise, use corresponding measures Original estimated hours, Remaining estimated hours, and Hours spent (they include values for all level issues, parent and sub-tasks, based on the report context). |
Remaining estimated hours change | Change (increase and decrease) in remaining estimated hours during the selected Time dimension period. For example, if there are logged hours in the period and the remaining estimated hours are adjusted automatically in Jira, "Remaining estimated hours change" would show the change equal to logged hours with a minus sign. On the other hand, if an issue gets estimated in the selected period, "Remaining estimated hours change" would show a change equal to added estimation. Import issue change history to get this measure. See also |
Remaining estimated hours history | Total of remaining estimated hours at the end of the selected Time dimension period for issues that match report filter criteria. Import issue change history to get this measure. |
Properties
eazyBI creates additional issue properties:
Issue Original estimated hours | If the Issue dimension is placed on rows and expanded to detailed issues, then the issue property Issue Original estimated hours shows the original estimated hours for individual issues. |
|---|---|
Issue hours spent | If the Issue dimension is placed on rows and expanded to detailed issues, then the issue property Issue hours spent shows the total time spent on individual issues. |