How can we improve Power BI?

Add Sprint meta data to Azure DevOps Connector

An Azure DevOps connector (currently in beta) is available for testing. We can extract a lot of data about the work items, and that is fine.

However - to provide more high-level insights to users, we need Sprint data as well.

So in short:

Please add these data artifacts to the possible items to extract:

* start time
* end time
* work items associated

Also - it would be great if numbers like "Team velocity" could be extracted as well.

Thank you :-)

4 votes
Sign in
Sign in with: facebook google
Signed in as (Sign out)

We’ll send you updates on this idea

Jesper Lund Stocholm shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →


Sign in
Sign in with: facebook google
Signed in as (Sign out)
  • david commented  ·   ·  Flag as inappropriate

    The more information that a visual needs to show, the slower that visual will be to stack. While this standard appears glaringly evident, it very well may be anything but difficult to overlook. For instance: assume you have an extensive dataset. On of that, you construct a report with a table of the table. End clients use slicers on the page to get to the lines they needed – normally they're just intrigued by a couple of dozen lines.

    A typical oversight is to have the default perspective on the table be unfiltered - that is, all 100M+ columns. The information for these lines must be stacked into memory and uncompressed at each revive. This made gigantic memory loads. The arrangement: decrease the maximum number of things that the table shown utilizing the "Top N" channel. The maximum thing can be a lot bigger than what clients would require, for instance, 10,000. Thus, the end-client experience was unaltered, yet memory use of the report dropped various requests of greatness, and execution improved as needs be.

Feedback and Knowledge Base

Ready to get started?

Try new features of Power BI today by signing up and learn more about our powerful suite of apps.