Cycle graph
Read cycle burndown for scope, started, and completed work as the cycle progresses.
The graph displays the progress you've made in your cycle.
Overview
The burndown appears once a cycle has begun and updates as work in the cycle changes. Open a cycle and show the details sidebar (Show sidebar) to see it. From Cycles, the current and completed rows also show the graph.
Upcoming cycles show capacity instead of a graph.
How to read a cycle graph
Scope is the total work in the cycle.
Ideal is the target completion path. It spends budget on working days and stays flat on non-working days. If completed work stays at or above this line, you are on track to finish in the cycle.
Started is work that has begun, stacked on top of completed.
Completed is work that is done. Bars under the lines make day-to-day completions easier to compare.
Hover a point for the exact values that day.
Understanding scope
Scope uses the team's estimate settings on Settings → Your teams → <team> → General. When estimates are on, the graph counts estimate points and follows the team's rule for issues without an estimate. When estimates are off, each issue counts as 1.
Assign completed issues to previous cycles
Turn on Completed issues in cycle automation to attribute newly completed work to the current cycle, or to the cycle that just ended if the team is in cooldown.
Issues that were in a cycle when it closed can still count toward that cycle if they finish during cooldown, before the next cycle starts.
FAQ
Last updated on