![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(89.60000000000001, 26%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGS%3C/text%3E%3C/svg%3E)
Azure
A cloud computing platform and infrastructure for building, deploying and managing applications and services through a worldwide network of Microsoft-managed datacenters.
hi Gage )
aha, tracking dropped story points can be a bit tricky, but let's break it down. u're already pulling data from the odata feed, so we're halfway there ))
u'll need to compare the sprint work items at two points in time. u can use the 'analytics' views in azure devops to get historical data. then, in power bi, pull the 'work item snapshot' entity from the odata feed. this gives u a timeline of work items, including when they were removed from the sprint.
a quick dax formula to calculate dropped story points
dropped story points =
calculate(
sum('work item snapshot'[story points]),
filter(
'work item snapshot',
'work item snapshot'[sprint start date] <= selected date
&& 'work item snapshot'[sprint end date] >= selected date
&& 'work item snapshot'[state] = "removed"
)
)
if u're using the 'work item history' table, u might need to filter for changes where the 'iteration path' was updated. this can be a bit messy, but it's worth looking into.
and hey, this approach isn't just for power bi. u can use similar logic in other tools that connect to azure devops, like excel or tableau.
hope this helps )) let me know if u hit any snags, and i'll try to untangle it with u.
ps. nice job digging into the odata feed it's a powerful tool once u get the hang of it!
Alex
and "yes" if you would follow me at Q&A - personaly thx.
P.S. If my answer help to you, please Accept my answer