Guide
Burn Down Chart
Let's create a Burn Down Chart for Sprint 1.0. It will be a chart that shows a number of "Done" Bugs and User Stories in Sprint:
Step 0: Pre-requisites
Bug and Story databases are connected to the Sprint database (have a relation).
Bug and Story has a Lookups field called Sprint Status. Create this field for both databases via New Field → Lookup → Sprint → Status. This is required to filter Bugs and Stories by current sprint.
Step 1. Create a Report View and choose Datasources
That will be a historical report and 90 days history period is ok for us. We will be analyzing Bugs & Stories, so they will be our sources
Step 2. Filter Data by the current Sprint
💡 No need for that, if you create Context reports using Smart Folders
We need this chart to be updated automatically, once we start a new Sprint. Both Bugs & User Stories have a Lookups field with the Sprint Status. It is calculated based on its duration. So, we can use that "common" field in our dynamic filter.
Step 3. Set X-axis Timeline function
Now we should set a TIMELINE function like this (note that the two last values are cut chart by release dates):
AUTO(
TIMELINE(
[Modification Date],
[Modification Valid To],
TRUE,
MIN([Sprint Dates Start]),
MAX([Sprint Dates End])
)
)
Step 4. Set Y-axis and chart type
In a Burn Down we calculate the remaining number of undone cards, so in Y-axis we will set a COUNTIF_DISTINCT formula
COUNTIF_DISTINCT(
[Id],
[State Final] != 'true'
)
Note: you can have many as many "Final" states as you want to. By default final state is Done
And we'll set Line as a chart type:
Step 5. Make this chart a bit more friendly
You can name the title and add the report description, so it was clear for everyone how it works
Step 6. Add an Ideal line
The ideal line should just move from the first to the last day of the Sprint and from the number of planned cards to zero. It can be created as an Annotation only, using this IDEAL_LINE function:
IDEAL_LINE(
FIRST([Bugs & Stories progress]),
0
)
Here is how you add a new Annotation line:
Step 7. Add a forecast line
The forecast line shows basic predictions about the Sprint completion date based on team velocity. We'll use the FORECAST_LINE function:
FORECAST_LINE(
[Bugs & Stories progress],
0
)
Noted:
If you want to check whether everything is calculated correctly, which cards had changed and etc. - anytime you can check the data source.