Use the Burnup Execution Report to compare accumulated completed testing with a planned baseline over a date range. It helps you see whether testing is progressing at the pace needed to finish the selected scope.
Read the chart
Chart element | Meaning |
Horizontal axis | Reporting dates. |
Vertical axis | The count of tests or completed testing items, according to the selected counting option. |
BASELINE line | The expected cumulative progress if the selected test scope is completed evenly across the reporting days. |
COMPLETED line | The cumulative completed count within the selected scope and date range. |
Completed includes finished Passed, Failed, and N/A results. A completed count does not mean all those tests passed. In-progress or blocked results do not count as completed.
Hover over a date to compare the two values. The baseline can extend into future reporting dates; completed results are shown through the current reporting date.
1. Add and configure the gadget
Open a Jira dashboard you can edit. Select Add gadget, search for Vansah - Burnup Execution Report, and add it.
Open the gadget configuration and select the Jira space.
Choose Work Item/Test Folder or Test Plan as the reporting scope. Select the work items, folders, or plans you want to include. Use Apply in selection panels before returning to the configuration.
Choose whether to enable Report by distinct Test Cases, as explained below.
Set the Start Date and End Date. Use the date settings beside Start Date to choose Every Day or Exclude Weekends.
Add any supported testing filters using More and choose their values. For sprint reporting, select the sprint filter and check the reporting dates yourself.
Select Save and wait for the report to load.
Select the Burnup Execution Report from Jira’s gadget directory.
2. Choose how completed testing is counted
Option | How the completed line is counted |
Report by distinct Test Cases selected | Counts a Test Case key once after it has a qualifying completed result within the report period. Completing it again in another selected requirement does not add another unique case. |
Report by distinct Test Cases cleared | Counts completed case-and-context combinations. The same case completed for two selected work items can contribute two completed items. Repeating it in the same context does not create another unique combination. |
For example, if DEMO-C46 is completed against both DEMO-123 and DEMO-124, distinct-case counting contributes one completed case. With the option cleared, those two work item contexts can contribute two completed items.
Test Plan scope also considers the selected plan’s testing context. Check the scope and counting option before comparing this report with another report’s totals.
3. Understand the baseline
Vansah takes the linked test scope used for the baseline and spreads it across the reporting days. The start and end dates are included. If you exclude weekends, weekend dates are omitted from the chart and the baseline schedule.
Example: a baseline scope of 20 tests across 5 reporting days gives a daily increment of 4.
Reporting day | Cumulative baseline |
1 | 4 |
2 | 8 |
3 | 12 |
4 | 16 |
5 | 20 |
Displayed baseline points are rounded. The baseline is calculated from the linked scope when the report is generated; changing the selected scope or linked tests can change it.
4. Inspect the daily data
Select Table data below the chart to expand the daily table. Maximizing the gadget is optional.
Review the period, execution totals, result breakdown, linked work items, case keys, and baseline.
Select a linked count or a supported completed chart point to inspect the contributing Test Cases. Baseline points do not open a case list.
This example shows the expanded report in an earlier layout. Use Table data in the current gadget.
Daily totals and the cumulative completed line answer different questions. Daily totals describe recorded activity for a date; the completed line accumulates the qualifying unique cases or case-and-context combinations across the period.
5. Export the report
Open the More menu (three dots) inside the report and select Export.
Choose XLSX or HTML, then select Export again.
Open the downloaded file and check its scope and dates against the gadget. Expand Table data before an HTML export if you want the daily table included.
When distinct-case counting is enabled, check the final columns of an XLSX download against the table. If the labels and values do not align, use HTML for sharing the visible report and contact Vansah support.
If the totals do not match your expectation
Check the Jira space, selected work items/folders/plans, report dates, weekend option, timezone, and testing filters.
Check whether distinct-case counting is selected. The same case in several requirements can be counted differently between modes.
Compare completed with passed results: failed and N/A executions can still be completed.
Refresh after changing the test scope. If the difference remains, share the configuration, date, and example case keys with Vansah support.
For general dashboard setup, see Set Up Vansah Gadgets on a Jira Dashboard.