Generate a report
Reporting helps you track and analyze your team's work throughout a project.
Jira has a range of reports that you can use to show information about your project, versions, epics, sprints, and work items.
Generating a report
To generate a report:
Navigate to the project you want to report on.
Select Reports from the project navigation. The reports overview page displays.
Make a selection to begin generating the report. View the list of reports below for more details of each report.
Company-managed projects support multiple boards. Jira runs reports on each board in the project. Ensure you're viewing the correct board before generating a report. Learn more about switching between boards in a company-managed project.
Reports for team-managed software projects
Burnup Chart
Applies to: Sprints
Provides a visual representation of a sprint's scope, as well as its remaining work.
This helps your team stay on track.
Velocity Chart
Applies to: 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.
Reports for Scrum projects
Burndown Chart
Applies to: 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
Applies to: 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
Applies to: 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 Chart
Applies to: 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
Applies to: Any period of time
Shows the statuses of work items over time.
This helps you identify potential bottlenecks that need to be investigated.
Epic Report
Applies to: 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
Applies to: 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
Applies to: 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
Applies to: 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
Applies to: 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
Control Chart
Applies to: 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
Applies to: Any period of time
Shows the statuses of work items over time.
This helps you identify potential bottlenecks that need to be investigated.
General reports for analyzing work items
Average Age Report
Shows the average age of unresolved work items for a project or filter. This helps you see whether your backlog is being kept up to date.
Created vs resolved work items report
Maps created work items versus resolved work items over a period of time. This helps you understand whether your overall backlog is growing or shrinking.
Created with Sketch.
Viewing the chart — Areas in red show periods where more work items were created than resolved. Areas in green show periods where more were resolved than created.
Pie Chart Report
Shows a pie chart of work items for a project or filter grouped by a specified field. This helps you see the breakdown of a set of work items, at a glance.
For example, you could create a chart to show work items grouped by Assignee for a particular version in a project (using a filter).
Recently created work items report
Shows the number of work items 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.
Viewing the chart — The green portion of the bar shows the created work items that are resolved. The red portion shows created but unresolved work items as yet.
Resolution Time Report
Shows the length of time taken to resolve a set of work items for a project or filter. This helps you identify trends and incidents that you can investigate further.
Single Level Group By Report
Shows work items 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 work items in a version of a project, grouped by Assignee.
Note that there is a display limit of 1,000 work items for this report.
Time Since work items Report
For a date field and project or filter, maps the work items against the date that the field was set. This can help you track how many work items were created, updated, etc over a period of time.
Time Tracking Report*
Shows time tracking information on work items for a particular version of a project.
The table in the report shows the work items 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 work item.
Estimated Time Remaining - The current estimate of the remaining amount of time it would take to complete this work item.
Time Spent - The amount of time spent on the work item. This is the aggregate amount of time that has been logged against this work item.
Accuracy- The accuracy of the original estimate compared to the current estimate for the work item. 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' work item (i.e. the sum of the work item'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 work items (green) and incomplete work items (orange).
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 work items in this version are ahead of or behind schedule.
There are three cases:
The work items are on schedule with the original estimate.
The Accuracy bar is completely blue and is the same length as the Progress bar above it.
The work items 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 work items are behind.
The work items 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 work items and 1,000 sub-tasks. You must have the Fix Version included in your work item 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 work items 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 work item) before a given version is complete.
For the specified version, you'll be able to see a list of unresolved work items 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 work items 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:
Change Log
Displays a list of work items from Jira. This list can be static or dynamic, automatically updating as the status of your work items 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 work 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 Partners are available for custom projects.
Work item filters can be exported to Microsoft Excel, where they can be further manipulated into charts and reports. See Working with search results.
Was this helpful?