Reporting

Reporting helps you track and analyze your team's work throughout a project.

Jira Software has a range of reports that you can use to show information about your project, versions, epics, sprints, and issues.



Generating a report

  1. Navigate to the desired board and click Reports. The last report viewed will be displayed.
  2. Click Switch report to view a different report. The reports in this list are specific to agile development.
    See the 'Reports for Scrum projects' or 'Reports for Kanban projects' sections below for more details.
  3. If you want to view reports that are not specific to agile development, select All reports from the Switch report drop-down, and view the reports that are not in the 'Agile' section. See the 'General reports for analyzing issues' section below for more details. 

Reports for Scrum projects

Chart Applies to Purpose
Burndown Chart Sprints

Tracks the total work remaining, and projects the likelihood of achieving the sprint goal.

This helps your team manage its progress and respond accordingly.

Burnup Chart Sprints

Provides a visual representation of a sprint's scope, as well as its remaining work.

This helps your team stay on track.

Sprint Report Sprints

Shows the work completed or pushed back to the backlog in each sprint.

This helps you determine if your team is overcommitting or if there is scope creep.

Control ChartControl Chart Projects, versions, or sprints

Shows the cycle time for your product, version, or sprint.

This helps you identify whether data from the current process can be used to determine future performance.

Cumulative Flow Diagram Any period of time

Shows the statuses of issues over time.

This helps you identify potential bottlenecks that need to be investigated.

Epic Report Epics

Shows the progress towards completing an epic over time.

This helps you manage your team's progress by tracking the remaining incomplete and unestimated work.

Epic Burndown Epics

Similar to the Epic Report, but optimized for Scrum teams that work in sprints. Tracks the projected number of sprints required to complete the epic.

This helps you monitor whether the epic will release on time, so you can take action if work is falling behind.

Release Burndown Versions

Similar to the Version Report, but optimized for Scrum teams that work in sprints.

Tracks the projected release date for a version. This helps you monitor whether the version will release on time, so you can take action if work is falling behind.

Velocity Chart Sprints

Tracks the amount of work completed from sprint to sprint.

This helps you determine your team's velocity, and estimate the work your team can realistically achieve in future sprints.

Version Report Versions

Tracks the projected release date for a version.

This helps you monitor whether the version will release on time, so you can take action if work is falling behind.

Reports for Kanban projects

Chart Applies to Purpose
Control Chart Projects, versions, or sprints

Shows the cycle time for your product, version, or sprint.

This helps you identify whether data from the current process can be used to determine future performance.

Cumulative Flow Diagram Any period of time

Shows the statuses of issues over time.

This helps you identify potential bottlenecks that need to be investigated.

Chart Purpose
Average Age Report Shows the average age of unresolved issues for a project or filter. This helps you see whether your backlog is being kept up to date.
Created vs Resolved Issues Report

Maps created issues versus resolved issues over a period of time. This helps you understand whether your overall backlog is growing or shrinking.

Notes...
  • Viewing the chart — Areas in red show periods where more issues were created than resolved. Areas in green show periods where more were resolved than created.
Pie Chart Report

Shows a pie chart of issues for a project or filter grouped by a specified field. This helps you see the breakdown of a set of issues, at a glance.

For example, you could create a chart to show issues grouped by Assignee for a particular version in a project (using a filter).

Recently Created Issues Report 

Shows the number of issues created over a period of time for a project or filter, and how many were resolved. This helps you understand if your team is keeping up with incoming work.

Notes...
  • Viewing the chart — The green portion of the bar shows the created issues that are resolved. The red portion shows created but unresolved issues as yet.
Resolution Time Report Shows the length of time taken to resolve a set of issues for a project or filter. This helps you identify trends and incidents that you can investigate further.
Single Level Group By Report 

Shows issues grouped by a particular field for a filter. This helps you group search results by a field, and see the overall status of each group. For example, you could view the issues in a version of a project, grouped by Assignee.

Note that there is a display limit of 1,000 issues for this report.

Time Since Issues Report  For a date field and project or filter, maps the issues against the date that the field was set. This can help you track how many issues were created, updated, etc over a period of time.
Time Tracking Report *

Shows time tracking information on issues for a particular version of a project.

Notes...

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 that 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 Accuracy graph. 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 Progress graph. 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.


Note that this report can only display up to 1,000 issues and 1,000 sub-tasks. You must have the Fix Version included in your issue configuration for this report to display data.

User Workload Report * 

Shows how much work a user has been allocated, and how long it should take.

For a specified user, you'll be able to see the number of unresolved issues assigned to the specified user, and the remaining workload, on a per-project basis.

Version Workload Report *

Shows how much outstanding work there is (per user and per issue) before a given version is complete.

For the specified version, you'll be able to see a list of unresolved issues assigned to each user, each user's workload, and a summary of the total remaining workload for the version.

Workload Pie Chart Report * Shows the relative workload for assignees of all issues for a project or filter.

Only available if your Jira administrator has enabled time tracking.

Reports available in Confluence

If you have connected Jira to Confluence, you can create the following reports in Confluence: 

Chart Purpose
Change Log Displays a list of issues from Jira. This list can be static or dynamic, automatically updating as the status of your issues change in Jira. 
Status Report The Status Report displays the progress of a Jira project and fix version in pie charts by status, priority, component, and issue type. The Status Report uses the Jira Chart macro, and is dynamic.

Other reports

  • Additional reports (e.g. Gantt Chart Report, Timesheet Report, Jira SQL Plugin) are available for download from the Atlassian Marketplace
  • Jira administrators can also create new reports with the plugin API — see our Tutorial - Creating a Jira report. If you don't want to build a plugin yourself, Atlassian Experts are available for custom projects. 
  • Issue filters can be exported to Microsoft Excel, where they can be further manipulated into charts and reports. See Working with search results.

What next?

You are done! Now the cycle begins again. You will probably be planning a new version, even as you wrap up an existing version. You might even be ready to start a new project. Check out the previous topics below:


Project lifecycle

  NEW PROJECT   BACKLOG    NEW VERSION    WORK    RELEASE    REPORTING

Last modified on May 7, 2018

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.