I’m working with Azure DevOps and need to create burndown charts that show detailed progress tracking. In JIRA, you can easily see how child work items roll up into their parent items on the burndown chart, which gives a really clear picture of sprint progress.
I want to know if Microsoft’s Azure DevOps has similar functionality where I can view burndown data that aggregates subtasks or child work items up to their parent user stories or features. This would help me track sprint progress more effectively and see which parent items are causing delays based on their child task completion.
Has anyone successfully configured this type of hierarchical burndown reporting in Azure DevOps? What are the steps to set it up?
Azure DevOps doesn’t have hierarchical burndown charts like JIRA, which can be frustrating for users who value that level of visibility. However, there are alternative methods to achieve similar results. One effective workaround involves using Analytics Views. You can create a view in your project settings that includes work item hierarchy relationships, and then utilize Power BI to generate reports that display parent-child relationships in your burndown data. Additionally, you might explore using Delivery Plans coupled with custom queries to monitor feature-level progress. Though it may not replicate a traditional burndown chart, this approach provides a comprehensive view of bottlenecks at the parent level. It requires some initial setup, but it can significantly enhance your understanding of sprint progress across different work item levels.
yup, Azure DevOps burndown charts are kinda lacking compared to JIRA. i managed to make the sprint burndown widget work a bit better by adjusting the query to pull in child items. it’s not ideal but it’s def better than the out-of-the-box setup. haven’t explored marketplace extensions tho, they could help.
I’ve hit this same problem moving from JIRA to Azure DevOps. The built-in burndown is pretty weak for tracking hierarchical stuff, but I found a workaround that actually works well. We use the Analytics service with custom queries to track completion percentages at the feature level. You need to link your user stories and tasks properly first, then build dashboard widgets that show remaining work rolled up by parent items. It’s not as smooth as JIRA, but you can tweak the sprint burndown widget to include child work items by editing the query. This way you can see which features are behind based on their task completion. Takes a bit of setup time, but you get the hierarchical view you want without buying extra tools.