Burndown chart
Navigation |
|---|
Report Usage
This report is a line chart showing the team’s progress toward goals over time. It displays two lines - guideline and actual - for comparing expected vs. actual progress. The Y-axis shows the metric value, and the X-axis shows the start and end dates.
Specific functionality:
This report gives information about the project status. Whether it is On track, Off track, or At risk.
For Story points and Issue count:
If the percentage of completed issues/story points is in the range of 85 - 89% - At risk.
If 90 - 100% of issues/story points completed - On track.
If the percentage is equal to or less than 84% - Off track.
For Remaining estimate:
Off Track: If the remaining estimate completion is equal to or less than 84%.
On Track: If the remaining estimate completion is 90% - 100%.
At Risk: If the remaining estimate completion is in the range of 85-89%.
In the top-left corner of the chart, selected data source is displayed, along with a clickable link that navigates to Jira.
While hovering the line tooltip appears. It shows the selected date (one the user is hovering over), guideline (showing the planned amount of completed values till the chosen moment), and unresolved value (amount of left values till the set due date).
Labels on the line shows unresolved value for each day and the difference with the guideline value. Labels can be added and removed.
The report is built considering all issue types.
Setting up a report
The report has 4 tabs of configurations: Data source, Parameters, Display, Description.
Data source & Description
This report supports filtering issues by Basic Source, Saved Filter, or JQL query. For full guidance on how to configure your data source and , see the Data Source & Report Description .
The report is built on actual data. After adding or removing issues from the Sprint or Version it will impact the initial amount of issues and report as a whole.
Specific Report Parameters
The Duration field is required. Users select a start and end date via a datepicker, setting the report’s timeframe (minimum 2 days, maximum 60 days).
Sprint specifics:
If a Sprint has a start and end date, they are auto-filled in Duration.
Custom Duration uses Sprint dates only if specified.
Version specifics:
If a Version has a start and end date, they are auto-filled in Duration.
The Metric field is required and defines the KPI for the report (e.g., Issue count, Story points, Remaining estimate). Default: Issue count.
The Include weekends toggle allows users to include or exclude weekends in the report.
Display
The Show label toggle enables/disables the dots that indicate a chosen period value.
Report Use Cases
✅ Assess whether your team is on track to complete sprint work based on issue count or story points.
✅ Monitor whether a version (release) is progressing as planned.
✅ Measure whether the team’s overall scope is trending toward timely completion.