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!Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes! Register now.
Hello Power BI Experts!
Here's an example of data I'm working with:
ID | Type | ParentID | RemainingHours |
1001 | Bug | ||
1002 | Task | 1001 | 8 |
1002 | Task | 1001 | 5 |
1003 | Task | 1001 | 1 |
1004 | Task | 1001 | 5 |
1004 | Task | 1001 | 2 |
1005 | Bug | ||
1006 | Task | 1005 | 3 |
1007 | Task | 1005 | 1 |
1007 | Task | 1005 | 0 |
1008 | Bug | ||
1009 | Bug | ||
1010 | Task | 1009 | 1 |
I'm having items of different types: Bug and Task.
Both are related, so I can see from my Task rows to which Bug they're linked to through the ParentID column.
The data contains history version for each item, so they can be duplicated to reflect different states (here, the number of RemainingHours decreasing).
I'm trying to put in place Measures (or Columns, I'm not sure what's feasible) in order to:
For example, the result should shows that:
Bug-1001 is linked to 3 Tasks, had 14 Hours planned and has 8 hours remaining.
Bug-1005 is linked to 2 Tasks, had 4 hours planned and has 3 hours remaining.
Bug-1008 is not linked to any Task
Bug-1009 is linked to 1 Task, had 1 hour planned and has 1 hour remaining.
So far, I've tried this (to have the number of planned hours):
Solved! Go to Solution.
hello, i have tried it using calculated columns as you can see on screenshot. i have used interim columns to come up with the planned/max remaining hours per bug and remaining hours per bug:
hello, i have tried it using calculated columns as you can see on screenshot. i have used interim columns to come up with the planned/max remaining hours per bug and remaining hours per bug:
Hello @Anonymous
I've tested your proposition and it works like a charm! Thank you so much!