Documentation for JIRA 4.0. Documentation for other versions of JIRA is available too.

Skip to end of metadata
Go to start of metadata

The Time Tracking Report displays useful time tracking information on issues for a particular version of a project. This report shows original and current time estimates for all the issues, and whether they are ahead of or behind the original schedule. (Note: this report is only available if time tracking has been enabled by your JIRA administrator).

On this page:

What does the 'Time Tracking' report look like?

The report generated will look something like this:

Screenshot: 'Time Tracking' report

Or, if sub-tasks are enabled, the report will look something like this:

The table in the report shows the issues within the version:

  • There are four time tracking fields as follows:
    • Original Estimate - The original estimate of the total amount of time it would take to complete this issue.
    • Estimated Time Remaining - The current estimate of the remaining amount of time it would take to complete this issue.
    • Time Spent - The amount of time spent on the issue. This is the aggregate amount of time which has been logged against this issue.
    • Accuracy- The accuracy of the original estimate compared to the current estimate for the issue. It is the difference between the sum of the Time Spent and Estimated Time Remaining fields, and the Original Estimate field.
  • If sub-tasks are enabled, the *'∑'*column at the right of the field shows the aggregate time tracking information for each 'parent' issue (i.e. the sum of the issue's own values plus those of its sub-tasks).
  • The last line of the table shows the aggregate time tracking information for the whole version.

The report also includes two bar-graphs (above the table) which represent the aggregate time tracking information for the version:

  • The first bar-graph ('Progress') shows the percentage of completed issues (green) and incomplete issues (orange) in this version:
  • The second bar-graph ('Accuracy' -blue) shows the accuracy of the original estimates.

The length of the Accuracy bar compared to the Progress bar indicates whether the issues in this version are ahead of or behind schedule. There are three cases:

  1. The issues are on schedule with the original estimate. The Accuracy bar is completely blue and is the same length as the Progress bar above it.
  2. The issues are behind the original estimate (i.e. will take longer than originally estimated). The Progress graph is longer than the Accuracygraph. The blue region represents the original estimated time, and the light-grey region is the amount of time by which issues are behind.
  3. The issues are ahead of the original estimate (i.e. will take less time than originally estimated). The Accuracy graph is longer than the Progressgraph. The blue bar represents the original estimated time, and the light-grey region represents the amount of time by which the original estimates were overestimated.

Generating a 'Time Tracking' report

To generate a Time Tracking Report:

  1. On the top navigation bar, click the white triangle next to 'Projects'. The projects dropdown will display.
    (tick) Tip: If you click on the 'Projects' link instead of the triangle, the summary for your current project will display.
  2. Click the project that you wish to browse. If it is not displayed in the dropdown, click 'View All Projects' — you will be able to view a list of all projects set up in your JIRA instance and select your project from there. (The choice of project will not affect the report.)
  3. Click the 'Reports' menu on the right of the page and click 'Time Tracking Report' from the dropdown menu that displays. The following form will appear:
  4. In the 'Version' drop-down list, select the version on which you wish to report. The report will include all issues that belong to this version, that is, all issues whose 'Fix Version' is this version.
  5. In the 'Sorting' drop-down list, choose how the issues in the report will be sorted:
    • Select 'Least completed issues first' to show issues with the highest 'Estimated Time Remaining first; or
    • Select 'Most completed issues first' to show issues with the lowest 'Estimated Time Remaining first.
  6. In the 'Issues' drop-down list, choose which issues will be included in the report:
    • Select 'All' to include all issues assigned to this version; or
    • Select 'Incomplete issues only' to exclude issues which are either completed (i.e. have an 'Estimated Time Remaining' of zero), or are not time-tracked (i.e. do not have an 'Original Estimate'). Note that issue status does not affect which issues are displayed.
  7. In the 'Sub-task Inclusion' drop-down list (note: this will only appear if sub-tasks are enabled), choose which sub-tasks will be included in the report, for all parent issues that belong to this version:
    • Select 'Only include sub-tasks with the selected version' to only include an issue's sub-tasks if the sub-tasks belong to the same version as the issue; or
    • Select 'Also include sub-tasks without a version set' to include an issue's sub-tasks if the sub-tasks belong to either the same version as the issue or to no version; or
    • Select 'Include all sub-tasks' to include all of an issue's sub-tasks, regardless of whether the sub-tasks belong to the same version, some other version or no version.Note: sub-tasks which belong to this version, but whose parent issues do not belong to this version, will always be included in the report.