Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
Need help in building Burnup : There are some SPRINT_NAME where few ISSUE_KEY , STORY_POINTS_COMMITTED gets changed when the Corresponding ISSUE_KEY are not completed and gets moved to Next SPRINT_NAME.
In the new SPRINT_NAME, their STORY_POINTS_COMMITTED gets changed Like in this case
ISSUE_KEY = ABC-81292 was started in SPRINT_NAME = Sprint 220 but was not completed (SPRINT_REPORT_STATUS = INCOMPLETED),
This was then moved to next Sprint SPRINT_NAME = Sprint 221 where STORY_POINTS_COMMITTED = 3 was assigned.
So i want to create a Burn_up chart on Commitment (STORY_POINTS_COMMITTED + STORY_POINTS_EXTRA_PULLED) and Completed (STORY_POINTS_COMPLETED + STORY_POINTS_EXTRA_COMPLETED) keeping in mind the Story point changes.
Can you please help in building Burnup chart with this data.
Here is the Data. I want to Build it FIX_VERSION wise
| BOARD_NAME | SPRINT_NAME | ISSUE_KEY | INITIAL_ESTIMATE | CURRENT_ESTIMATE | SPRINT_REPORT_STATUS | IS_ADDED_DURING_SPRINT | STORY_POINTS_COMMITTED | STORY_POINTS_EXTRA_PULLED | STORY_POINTS_COMPLETED | STORY_POINTS_EXTRA_COMPLETED | STORY_POINTS_NOT_COMPLETED | STORY_POINTS_REMOVED | ISSUE_TYPE_NAME | ISSUE_STATUS_NAME | PRIORITY | RESOLUTION | PROJECT_KEY | CREATED | Detailed_Affected_Version | Story_Points | FIX_VERSION | STATE | START_DATE | END_DATE | COMPLETE_DATE |
| ABC Scrum | Sprint 222 | ABC-81292 | 3 | 3 | INCOMPLETED | FALSE | 3 | 0 | 0 | 0 | 3 | 0 | Story | Resolved | Major | Fixed | ABC | 30-01-2025 16:20:25 +00:00 | null | 3 | 25.07 | closed | 15-03-2025 15:30:03 +00:00 | 04-04-2025 17:00:00 +00:00 | 05-04-2025 18:04:00 +00:00 |
| ABC Scrum | Sprint 221 | ABC-81292 | 3 | 3 | INCOMPLETED | FALSE | 3 | 0 | 0 | 0 | 3 | 0 | Story | Resolved | Major | Fixed | ABC | 30-01-2025 16:20:25 +00:00 | null | 3 | 25.07 | closed | 22-02-2025 09:59:50 +00:00 | 14-03-2025 17:00:00 +00:00 | 15-03-2025 15:28:56 +00:00 |
| ABC Scrum | Sprint 223 | ABC-81292 | 3 | 3 | INCOMPLETED | FALSE | 3 | 0 | 0 | 0 | 3 | 0 | Story | Resolved | Major | Fixed | ABC | 30-01-2025 16:20:25 +00:00 | null | 3 | 25.07 | closed | 05-04-2025 18:04:37 +00:00 | 25-04-2025 16:00:00 +00:00 | 27-04-2025 19:38:44 +00:00 |
| ABC Scrum | Sprint 220 | ABC-81292 | 0 | 3 | INCOMPLETED | FALSE | 3 | 0 | 0 | 0 | 3 | 0 | Story | Resolved | Major | Fixed | ABC | 30-01-2025 16:20:25 +00:00 | null | 3 | 25.07 | closed | 01-02-2025 14:31:27 +00:00 | 21-02-2025 17:00:00 +00:00 | 22-02-2025 09:58:28 +00:00 |
| ABC Scrum | Sprint 224 | ABC-81292 | 3 | 3 | REMOVED | FALSE | 3 | 0 | 0 | 0 | 0 | 3 | Story | Resolved | Major | Fixed | ABC | 30-01-2025 16:20:25 +00:00 | null | 3 | 25.07 | active | 27-04-2025 19:39:43 +00:00 | 16-05-2025 16:00:00 +00:00 | null |
| ABC Scrum | Sprint 222 | ABC-82115 | 2 | 3 | INCOMPLETED | FALSE | 3 | 0 | 0 | 0 | 3 | 0 | Story | Validation | Major | null | ABC | 24-02-2025 10:17:21 +00:00 | null | 3 | 25.07 | closed | 15-03-2025 15:30:03 +00:00 | 04-04-2025 17:00:00 +00:00 | 05-04-2025 18:04:00 +00:00 |
| ABC Scrum | Sprint 221 | ABC-82115 | 0 | 2 | INCOMPLETED | TRUE | 0 | 2 | 0 | 0 | 2 | 0 | Story | Validation | Major | null | ABC | 24-02-2025 10:17:21 +00:00 | null | 3 | 25.07 | closed | 22-02-2025 09:59:50 +00:00 | 14-03-2025 17:00:00 +00:00 | 15-03-2025 15:28:56 +00:00 |
| ABC Scrum | Sprint 224 | ABC-82115 | 3 | 3 | INCOMPLETED | FALSE | 3 | 0 | 0 | 0 | 3 | 0 | Story | Validation | Major | null | ABC | 24-02-2025 10:17:21 +00:00 | null | 3 | 25.07 | active | 27-04-2025 19:39:43 +00:00 | 16-05-2025 16:00:00 +00:00 | null |
| ABC Scrum | Sprint 223 | ABC-82115 | 3 | 3 | INCOMPLETED | FALSE | 3 | 0 | 0 | 0 | 3 | 0 | Story | Validation | Major | null | ABC | 24-02-2025 10:17:21 +00:00 | null | 3 | 25.07 | closed | 05-04-2025 18:04:37 +00:00 | 25-04-2025 16:00:00 +00:00 | 27-04-2025 19:38:44 +00:00 |
I want to build something like this : I want to Present Commitment which gets cummulative as and when Sprint progress and Completed the same way.
Solved! Go to Solution.
Hi @JeevanMallya ,
Thank you for reaching out to Microsoft Fabric Community.
Here are some steps to follow to achieve the requirement:
1.Create a Separate Sprint Table
This avoids circular dependency and helps us sort properly.
Go to Modeling → New Table (SprintTable)--You can find logic in attached .pbix file.
2.Sort Sprint Name
After table is created:
Go to SprintTable - Click on SPRINT_NAME
Choose Sort by Column - Select SprintOrder
3.you must create a relationship between SprintTable and your main data table (Sheet1) to allow proper filtering and avoid DAX errors.(Check in .pbix file)
4.Created 4 measures as shown in pbix file.(1.Committed 2.Completed 3.Cumulative_Committed 4.Cumulative_Completed.)
5.Build the Burn up Chart
Use a Line Chart:
X-axis: SprintTable[SPRINT_NAME]
Y-axis:Cumulative_Committed,Cumulative_Completed.
If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!
Hi @JeevanMallya ,
I hope this information is helpful. Please let me know if you have any further questions or if you'd like to discuss this further. If this answers your question, please accept it as a solution and give it a 'Kudos' so other community members with similar problems can find a solution faster.
Thank you.
Hi @JeevanMallya ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you.
Hi @JeevanMallya ,
May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you
Hi @JeevanMallya ,
Thank you for reaching out to Microsoft Fabric Community.
Here are some steps to follow to achieve the requirement:
1.Create a Separate Sprint Table
This avoids circular dependency and helps us sort properly.
Go to Modeling → New Table (SprintTable)--You can find logic in attached .pbix file.
2.Sort Sprint Name
After table is created:
Go to SprintTable - Click on SPRINT_NAME
Choose Sort by Column - Select SprintOrder
3.you must create a relationship between SprintTable and your main data table (Sheet1) to allow proper filtering and avoid DAX errors.(Check in .pbix file)
4.Created 4 measures as shown in pbix file.(1.Committed 2.Completed 3.Cumulative_Committed 4.Cumulative_Completed.)
5.Build the Burn up Chart
Use a Line Chart:
X-axis: SprintTable[SPRINT_NAME]
Y-axis:Cumulative_Committed,Cumulative_Completed.
If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!
| User | Count |
|---|---|
| 19 | |
| 9 | |
| 8 | |
| 7 | |
| 6 |