Burn Up
The main goal of a burn up chart is to show how a defined scope of work is completed to meet the desired milestone in a concrete period of time. We don't have a predefined burn up template for your boards since the platform cannot yet automatically recognize the semantics of your lists. This means that it is not clear to the application what items in the list are in your backlog, in progress, or completed.
We are going to show you how to build a burn up from scratch. We'll be using the public board of SUBNAUTICA (thank you guys for the great live sample).
Create a new report with "History of cards" as your source, then select board and period. Check the "Cumulative" option, since we need to include records that had changes made before the selected interval.
Let's drop the Timeline field on the X axis. This creates a historical calculation of date intervals distribution.
The next thing to do is configure a total count of records line to build the scope of cards yet to be completed. We need to have a criterion, like the iteration tag of the card we need to analyze, or the name of your ''Backlog'' list with items completed before the selected date range in order to exclude them. In this example, we'll just exclude cards from the list named Backlog.
Click the "+" sign on the Y axis, and then provide the total scope calculation. In our case, it looks like this: COUNTIF_DISTINCT([Card Id],NOT(LIKE([List], '%Backlog%')) AND NOT(LIKE([List], '%Done%') and [Date] < [Timeline Start])). In this example, the total scope of cards to be done is formed from all cards which are not in the backlog and were not completed before the start of the selected date range.
NOTE: If you're using sprint boards like this one, you don't need to filter out cards for the scope line. Feel free to use COUNT_DISTINCT([Card Id]) since all cards on your board should be done.
Now we need to build a line which shows how cards are completed during the desired period. For this, we need to add a calculation to the Y axis based on a count of cards count dropped into final (done) lists after the date range's start date. For SUBNAUTICA, the calculation looks like this: COUNTIF_DISTINCT([Card Id], LIKE([List], ‘%Done%’) AND [Date] >= [Timeline Start]).
Let's add an ideal line to show when the defined scope should be completed in an ideal world. We'll use annotations for this by providing a calculation for the Total Scope dimension: IDEAL_LINE(FIRST([Completed]), LAST([Total Scope])).
Sometimes, it can be quite useful to see an approximate forecast on when cards will actually be completed. Let's add the corresponding annotation for that: FORECAST_LINE([Completed], LAST([Total Scope])).
A total scope basic line also can be added in the same way: LAST([Total Scope]).
Finally, we get the Burn up Chart shown below. We know it's not easy thing to learn at first, but we believe that after some practice, you will be able to build much trickier things like a pro.
