Skip to content

Commit 0f69791

Browse files
committed
Simplifying work tracking sample power bi reports.
AB#29208: Create a Power Bi report (Power BI, New, Phase 3) AB#29047: Transform Analytics data to generate Power BI reports (Power BI, New, Phase 3) AB#29205: Open bugs or user stories sample reports (Power BI, New, Phase 3)
1 parent bd1c798 commit 0f69791

11 files changed

+249
-143
lines changed

docs/report/extend-analytics/odata-query-guidelines.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -262,7 +262,7 @@ For example, the following query gets a single work item by its identifier.
262262
> &$select=WorkItemId, Title
263263
> ```
264264
265-
If you're not sure which properties you should include in such a filter, you can look it up in the metadata. See [Explore the Analytics OData metadata](analytics-metadata.md). Properties are in the `Key` element of the `EntityType`. For example, `WorkItemId` and `Revision` are key columns for the `WorkItemRevision` entity.
265+
If you're not sure which properties you should include in such a filter, you can look it up in the metadata. See [Construct OData queries for Analytics, URL components to query the metadata](../analytics/analytics-query-parts.md#query-metadata). Properties are in the `Key` element of the `EntityType`. For example, `WorkItemId` and `Revision` are key columns for the `WorkItemRevision` entity.
266266
267267
> [!div class="tabbedCodeSnippets"]
268268
> ```XML
@@ -921,10 +921,10 @@ Another useful annotation is `Org.OData.Capabilities.V1.ExpandRestrictions`, whi
921921
922922
## Related articles
923923
924+
- [Construct OData queries for Analytics](../analytics/analytics-query-parts.md)
924925
- [Query work item tracking data](wit-analytics.md)
925926
- [Aggregate data](aggregated-data-analytics.md)
926927
- [Query trend data](querying-for-trend-data.md)
927928
- [Query work item links](work-item-links.md)
928-
- [Explore the Analytics OData metadata](analytics-metadata.md)
929929
- [Supported functions & clauses](odata-supported-features.md)
930930
- [Work tracking, process, and project limits](../../organizations/settings/work/object-limits.md)

docs/report/powerbi/create-report.md

+55
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,55 @@
1+
---
2+
title:Power BI data transformations
3+
titleSuffix: Azure DevOps
4+
description: Learn how to create a Power BI report from Analytics data.
5+
ms.subservice: azure-devops-analytics
6+
ms.custom: powerbi
7+
ms.author: kaelli
8+
author: KathrynEE
9+
ms.topic: how-to
10+
monikerRange: '>= azure-devops-2019'
11+
ms.date: 12/05/2022
12+
---
13+
14+
# Create a Power Bi report
15+
16+
17+
[!INCLUDE [version-gt-eq-2019](../../includes/version-gt-eq-2019.md)]
18+
19+
Link to Power BI report creation. Link to previous articles to get the data.
20+
21+
Once you've imported or connected your data to Power BI and transformed the data, you're ready to create your report. You create a report through these steps:
22+
23+
1. Choose the type of report your want.
24+
2. Choose the fields to use in the report - the number of fields will depend on the report you select.
25+
26+
27+
## Understand your report options
28+
29+
:::image type="content" source="media/create-powerbi-report/visualizations.png" alt-text="Screenshot of Power BI Visualizations choices.":::
30+
31+
32+
33+
## Create a Pie chart
34+
35+
## Create a Visualization matrix report
36+
37+
[Create matrix visualizations in Power BI](/power-bi/visuals/desktop-matrix-visual)
38+
39+
## Create a Stacked bar report
40+
41+
## Create a Trend report
42+
43+
## Create a Clustered column chart
44+
45+
## Related articles
46+
47+
48+
- [Get started with Power BI Desktop](/power-bi/fundamentals/desktop-getting-started)
49+
- [Quickstart: Connect to data in Power BI Desktop](/power-bi/connect-data/desktop-quickstart-connect-to-data)
50+
- [Use the ribbon in Power BI Desktop](/power-bi/create-reports/desktop-ribbon)
51+
52+
53+
## Power BI articles
54+
55+
- [Create matrix visualizations in Power BI](/power-bi/visuals/desktop-matrix-visual)

docs/report/powerbi/includes/query-filters-pipelines.md

+3-19
Original file line numberDiff line numberDiff line change
@@ -3,29 +3,13 @@ ms.subservice: azure-devops-analytics
33
ms.author: kaelli
44
author: KathrynEE
55
ms.topic: include
6-
ms.date: 09/21/2021
6+
ms.date: 12/05/2022
77
---
88

99
## Query filters
1010

11-
To determine available query filters, query the metadata as described in [Explore the Analytics OData metadata](../../extend-analytics/analytics-metadata.md). You can filter your queries using any of the **NavigationPropertyBinding Path** values listed under an **EntitySet**. To learn more about the data type of each value, review the metadata provided for the corresponding **EntityType**. Each **EntitySet** corresponds to the singular value for an **EntityType**.
1211

13-
For example, the **EntitySet Name="PipelineRunActivityResults"** corresponds to the **EntityType Name="PipelineRunActivityResult"**. The OData metadata for **EntitySet Name="PipelineRunActivityResults"** is as shown below for **v4.0-preview**. You can add filters based on any of the listed **NavigationPropertyBinding Path** values.
14-
15-
> [!div class="tabbedCodeSnippets"]
16-
> ```XML
17-
> <EntitySet Name="PipelineRunActivityResults" EntityType="Microsoft.VisualStudio.Services.Analytics.Model.PipelineRunActivityResult">
18-
> <NavigationPropertyBinding Path="Project" Target="Projects"/>
19-
> <NavigationPropertyBinding Path="Pipeline" Target="Pipelines"/>
20-
> <NavigationPropertyBinding Path="PipelineTask" Target="PipelineTasks"/>
21-
> <NavigationPropertyBinding Path="PipelineJob" Target="PipelineJobs"/>
22-
> <NavigationPropertyBinding Path="Branch" Target="Branches"/>
23-
> <NavigationPropertyBinding Path="PipelineRunQueuedOn" Target="Dates"/>
24-
> <NavigationPropertyBinding Path="PipelineRunStartedOn" Target="Dates"/>
25-
> <NavigationPropertyBinding Path="PipelineRunCompletedOn" Target="Dates"/>
26-
> <NavigationPropertyBinding Path="ActivityStartedOn" Target="Dates"/>
27-
> <NavigationPropertyBinding Path="ActivityCompletedOn" Target="Dates"/>
28-
> </EntitySet>
29-
> ```
12+
To determine available query filters, query the metadata as described in [Construct OData queries for Analytics, URL components to query the metadata](../../analytics/analytics-query-parts.md#query-metadata). You can filter your queries using any of the `Property` under an `EntityType` or `NavigationPropertyBinding Path` values listed under an `EntitySet`. Each `EntitySet` corresponds to an `EntityType`. For example, the `EntitySet Name="PipelineRunActivityResults"` corresponds to the `EntityType Name="PipelineRunActivityResult"`.
3013

14+
To learn more about the data type of each value, review the metadata provided for the corresponding `EntityType`.
3115

docs/report/powerbi/includes/query-filters-test.md

+3-17
Original file line numberDiff line numberDiff line change
@@ -3,28 +3,14 @@ ms.subservice: azure-devops-analytics
33
ms.author: kaelli
44
author: KathrynEE
55
ms.topic: include
6-
ms.date: 09/21/2021
6+
ms.date: 12/05/2022
77
---
88

99
## Query filters
1010

11-
To determine available query filters, query the metadata as described in [Explore the Analytics OData metadata](../../extend-analytics/analytics-metadata.md). You can filter your queries using any of the **NavigationPropertyBinding Path** values listed under an **EntitySet**. To learn more about the data type of each value, review the metadata provided for the corresponding **EntityType**. Each **EntitySet** corresponds to the singular value for an **EntityType**.
1211

12+
To determine available query filters, query the metadata as described in [Construct OData queries for Analytics, URL components to query the metadata](../../analytics/analytics-query-parts.md#query-metadata). You can filter your queries using any of the `Property` under an `EntityType` or `NavigationPropertyBinding Path` values listed under an `EntitySet`. Each `EntitySet` corresponds to an `EntityType`. For example, the `EntitySet Name="TestPoints"` corresponds to the `EntityType Name="TestPoint"`.
1313

14-
For example, the **EntitySet Name="TestPoints"** corresponds to the **EntityType Name="TestPoint"**. The OData metadata for the **EntitySet Name="TestPoints"** is as shown below for **v4.0-preview**. You can add filters based on any of the listed **NavigationPropertyBinding Path** values.
15-
16-
> [!div class="tabbedCodeSnippets"]
17-
> ```XML
18-
> <EntitySet Name="TestPoints" EntityType="Microsoft.VisualStudio.Services.Analytics.Model.TestPoint">
19-
> <NavigationPropertyBinding Path="ChangedOn" Target="Dates"/>
20-
> <NavigationPropertyBinding Path="Project" Target="Projects"/>
21-
> <NavigationPropertyBinding Path="TestSuite" Target="TestSuites"/>
22-
> <NavigationPropertyBinding Path="TestConfiguration" Target="TestConfigurations"/>
23-
> <NavigationPropertyBinding Path="TestCase" Target="WorkItems"/>
24-
> <NavigationPropertyBinding Path="Tester" Target="Users"/>
25-
> <NavigationPropertyBinding Path="AssignedTo" Target="Users"/>
26-
> <Annotation Term="Org.OData.Display.V1.DisplayName" String="Test Points"/>
27-
> </EntitySet>
28-
> ```
14+
To learn more about the data type of each value, review the metadata provided for the corresponding `EntityType`.
2915

3016

docs/report/powerbi/includes/query-filters-work-items.md

+3-30
Original file line numberDiff line numberDiff line change
@@ -3,40 +3,13 @@ ms.subservice: azure-devops-analytics
33
ms.author: kaelli
44
author: KathrynEE
55
ms.topic: include
6-
ms.date: 09/21/2021
6+
ms.date: 12/05/2022
77
---
88

99
## Query filters
1010

11-
To determine available query filters, query the metadata as described in [Explore the Analytics OData metadata](../../extend-analytics/analytics-metadata.md). You can filter your queries using any of the **NavigationPropertyBinding Path** values listed under an **EntitySet**. To learn more about the data type of each value, review the metadata provided for the corresponding **EntityType**. Each **EntitySet** corresponds to an **EntityType**.
11+
To determine available query filters, query the metadata as described in [Construct OData queries for Analytics, URL components to query the metadata](../../analytics/analytics-query-parts.md#query-metadata). You can filter your queries using any of the `Property` under an `EntityType` or `NavigationPropertyBinding Path` values listed under an `EntitySet`. Each `EntitySet` corresponds to an `EntityType`. For example, the `EntitySet Name="WorkItemSnapshot"` corresponds to the `EntityType Name="WorkItemSnapshot"`.
1212

13-
For example, the **EntitySet Name="WorkItemSnapshot"** corresponds to the **EntityType Name="WorkItemSnapshot"**. The OData metadata for **EntitySet Name="WorkItemSnapshot"** is as shown below for **v4.0-preview**. You can add filters based on any of the listed **NavigationPropertyBinding Path** values.
14-
15-
> [!div class="tabbedCodeSnippets"]
16-
> ```XML
17-
> <EntitySet Name="WorkItemSnapshot" EntityType="Microsoft.VisualStudio.Services.Analytics.Model.WorkItemSnapshot">
18-
> <NavigationPropertyBinding Path="Date" Target="Dates"/>
19-
> <NavigationPropertyBinding Path="RevisedOn" Target="Dates"/>
20-
> <NavigationPropertyBinding Path="Teams" Target="Teams"/>
21-
> <NavigationPropertyBinding Path="Processes" Target="Processes"/>
22-
> <NavigationPropertyBinding Path="Project" Target="Projects"/>
23-
> <NavigationPropertyBinding Path="Area" Target="Areas"/>
24-
> <NavigationPropertyBinding Path="Iteration" Target="Iterations"/>
25-
> <NavigationPropertyBinding Path="AssignedTo" Target="Users"/>
26-
> <NavigationPropertyBinding Path="ChangedBy" Target="Users"/>
27-
> <NavigationPropertyBinding Path="CreatedBy" Target="Users"/>
28-
> <NavigationPropertyBinding Path="ActivatedBy" Target="Users"/>
29-
> <NavigationPropertyBinding Path="ClosedBy" Target="Users"/>
30-
> <NavigationPropertyBinding Path="ResolvedBy" Target="Users"/>
31-
> <NavigationPropertyBinding Path="Tags" Target="Tags"/>
32-
> <NavigationPropertyBinding Path="ChangedOn" Target="Dates"/>
33-
> <NavigationPropertyBinding Path="ClosedOn" Target="Dates"/>
34-
> <NavigationPropertyBinding Path="CreatedOn" Target="Dates"/>
35-
> <NavigationPropertyBinding Path="ResolvedOn" Target="Dates"/>
36-
> <NavigationPropertyBinding Path="StateChangeOn" Target="Dates"/>
37-
> <NavigationPropertyBinding Path="InProgressOn" Target="Dates"/>
38-
> <NavigationPropertyBinding Path="CompletedOn" Target="Dates"/>
39-
> </EntitySet>
40-
> ```
13+
To learn more about the data type of each value, review the metadata provided for the corresponding `EntityType`.
4114

4215

Loading

0 commit comments

Comments
 (0)