Forum Discussion

db042190's avatar
db042190
Icon for Impactful Individual rankImpactful Individual
2 months ago
Solved

pbi and devops

hi is it true that the project mgt piece (epics etc) of devops can be seen by pbi? perhaps because that data is also in the "dataverse"?   i learned yesterday that the query feature in devops cant ...
Need Help
  • Parchitect's avatar
    Parchitect
    2 months ago

    Yes, but not because the data is in Dataverse.

    Power BI can report on Azure DevOps Boards data through Azure DevOps Analytics. That includes work items such as Epics, Features, User Stories, Tasks, Bugs, etc.

    The built-in connector is Azure DevOps (Boards only), but that uses Analytics Views. Those are useful for simple reporting, but they return a flat list of work items and are not ideal when you need a cross-project capacity view.

     

    For your scenario, I would start with the Azure DevOps Analytics OData endpoint instead. With OData, you can query at the organization level by omitting the project from the URL:

    https://analytics.dev.azure.com/{organization}/_odata/v4.0-preview/WorkItems

    Then bring that into Power BI using Get Data > OData feed, and start with a small set of fields:

    • Project
    • WorkItemId
    • WorkItemType
    • Title
    • State
    • AssignedTo
    • Iteration Path
    • Area Path
    • Story Points, Effort, or Remaining Work, depending on your process template

     

    One caution: assigned work and true developer capacity are not always the same thing. Work item data can show effort or remaining work, but if you need actual team capacity settings from Azure DevOps, that might require a separate API/export.

    So yes, Power BI is a good option here. I would just use Azure DevOps Analytics/OData as the source, not Dataverse.

     

    Useful references:

    Best regards,
    Parchitect - Solution Architect

    💡Did my response help you? Clicking Kudos is a small gesture that goes a long way, it encourages contributors and helps the community thrive!
    ✔️Did I answer your question? Please mark my post as a Solution, it helps others find the answer faster.

     

Parchitect's avatar
Parchitect
Icon for Solution Sage rankSolution Sage
2 months ago

Yes, but not because the data is in Dataverse.

Power BI can report on Azure DevOps Boards data through Azure DevOps Analytics. That includes work items such as Epics, Features, User Stories, Tasks, Bugs, etc.

The built-in connector is Azure DevOps (Boards only), but that uses Analytics Views. Those are useful for simple reporting, but they return a flat list of work items and are not ideal when you need a cross-project capacity view.

 

For your scenario, I would start with the Azure DevOps Analytics OData endpoint instead. With OData, you can query at the organization level by omitting the project from the URL:

https://analytics.dev.azure.com/{organization}/_odata/v4.0-preview/WorkItems

Then bring that into Power BI using Get Data > OData feed, and start with a small set of fields:

  • Project
  • WorkItemId
  • WorkItemType
  • Title
  • State
  • AssignedTo
  • Iteration Path
  • Area Path
  • Story Points, Effort, or Remaining Work, depending on your process template

 

One caution: assigned work and true developer capacity are not always the same thing. Work item data can show effort or remaining work, but if you need actual team capacity settings from Azure DevOps, that might require a separate API/export.

So yes, Power BI is a good option here. I would just use Azure DevOps Analytics/OData as the source, not Dataverse.

 

Useful references:

Best regards,
Parchitect - Solution Architect

💡Did my response help you? Clicking Kudos is a small gesture that goes a long way, it encourages contributors and helps the community thrive!
✔️Did I answer your question? Please mark my post as a Solution, it helps others find the answer faster.