Updates to feature progress report

AB#48647: Feature Progress rollup sample Power BI report (Power BI, New, Phase 3)
AB#29135: CFD report
AB#29140: Cycle time and lead time control charts - Azure DevOps Services

Author: KathrynEE

docs/report/powerbi/create-quick-report-odataq.md

@@ -124,8 +124,7 @@ Power BI shows you the fields you can report on.
 > [!NOTE]   
 > The example below assumes that no one renamed any columns. 
 
-> [!div class="mx-imgBorder"] 
-> ![Sample - Boards Rollup - Fields](media/odatapowerbi-bugtrend-fields.png)
+:::image type="content" source="media/reports-boards/bug-trends-selections.png" alt-text="Screenshot of Power BI Visualizations and Fields selections for Bug trends report. ":::
 
 For a simple report, do the following steps:
 
@@ -138,13 +137,9 @@ For a simple report, do the following steps:
 
 The example report:
 
-> [!div class="mx-imgBorder"] 
-> ![Sample - Boards Rollup - Report](media/odatapowerbi-bugtrend-report.png)
-
-[!INCLUDE [temp](includes/sample-multipleteams.md)]
-
-<a id="q-a">  </a>
 
+:::image type="content" source="media/odatapowerbi-bugtrend-report.png" alt-text="Screenshot of Sample Bug trends line chart report.":::
+ 
 ## Next steps
 
 > [!div class="nextstepaction"]

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

@@ -7,6 +7,6 @@ ms.date: 12/05/2022
 ---
 
 > [!NOTE]   
-> To determine available properties for filter or report purposes, see [Metadata reference for Azure Boards](../analytics/entity-reference-boards.md).  You can filter your queries or return properties using any of the `Property` values under an `EntityType` or `NavigationPropertyBinding Path` values available with an `EntitySet`. Each `EntitySet` corresponds to an `EntityType`. To learn more about the data type of each value, review the metadata provided for the corresponding `EntityType`.  
+> To determine available properties for filter or report purposes, see [Metadata reference for Azure Boards](../../analytics/entity-reference-boards.md).  You can filter your queries or return properties using any of the `Property` values under an `EntityType` or `NavigationPropertyBinding Path` values available with an `EntitySet`. Each `EntitySet` corresponds to an `EntityType`. To learn more about the data type of each value, review the metadata provided for the corresponding `EntityType`.  
 
 

docs/report/powerbi/media/reports-boards/bug-trends-report.png

@@ -15,11 +15,9 @@ ms.date: 12/08/2022
 
 [!INCLUDE [version-gt-eq-2019](../../includes/version-gt-eq-2019.md)]
 
-This article shows you how to display, for a given set of open Bugs, the number of Bugs in each State, trended over a period of time. The following image shows an example of such a trend. 
-
-
-:::image type="content" source="media/odatapowerbi-bugtrend-report.png" alt-text="Screenshot of Bug trends sample line chart report.":::
+Bug trend reports are useful to see how well a team is closing active bugs. This article shows you how to display the number of bugs in a given state over a period of time. The following image shows an example of a bug trends report.  
 
+:::image type="content" source="media/reports-boards/bug-trends-report.png" alt-text="Screenshot of Bug trends line chart report.":::
 
 
 [!INCLUDE [temp](includes/sample-required-reading.md)]
@@ -86,7 +84,7 @@ https://analytics.dev.azure.com/{organization}/{project}/_odata/v3.0-preview/Wor
 - `{organization}` - Your organization name 
 - `{project}` - Your team project name, or omit "/{project}" entirely, for a cross-project query 
 - `{areapath}` - Your Area Path. Example format: `Project\Level1\Level2`
-- `{startdate}` - The date to start your trend report. Format: YYYY-MM-DDZ. Example: `2019-04-01Z` represents 2019-April-01. Don't enclose in quotes.
+- `{startdate}` - Start your report for items completed on or after a given date with the format: `YYYY-MM-DDZ`. For example: `2022-04-01Z` represents 2022-April-01. Don't enclose in quotes.
 
 <!--- How specify the end date? --> 
 
@@ -186,7 +184,7 @@ The following table describes each part of the query.
 
 
 
-### Bug trends filtered by Teams 
+### Bug trend filtered by Teams 
 
 You can query for bug trends by team name rather than Area Path.  
 
@@ -283,7 +281,7 @@ https://analytics.dev.azure.com/{organization}/{project}/_odata/v3.0-preview/Wor
 
 <a id="weekly-snapshots" />
 
-### Bug trends with a snapshot on the first of every month
+### Bug trend with a snapshot on the first of every month
 
 Using a monthly snapshot reduces the amount of data pulled into Power BI, and increases query performance. 
 
@@ -336,50 +334,39 @@ https://analytics.dev.azure.com/{organization}/{project}/_odata/v3.0-preview/Wor
 [!INCLUDE [temp](includes/rename-query.md)]
 
 
-## Transform data in Power BI
-
-
-
-### Expand columns in Power BI
+## Expand columns in Power BI
 
 Expand the `Area/AreaPath)` and `Iteration/IterationPath` columns. Expanding the columns flattens the record into specific fields. To learn how, see [Transform Analytics data to generate Power BI reports](transform-analytics-data-report-generation.md). 
 
 
-### (Optional) Rename fields
+## (Optional) Rename fields
 
 Once you have expanded the columns, you may want to rename one or more fields. For example, you can rename the column `AreaPath` to `Area Path`. To learn how, see [Rename column fields](transform-analytics-data-report-generation.md#rename-column-fields). 
 
 
-### (Optional) Rename query 
-
-You can the default query label, *Query1* to something more meaningful. To do so, see [Rename the query](transform-analytics-data-report-generation.md#rename-the-query).  
-
-
 ## Create the Line chart report 
 
 1. In Power BI, choose the **Line chart** report under **Visualizations** and select the fields as shown in the following image. 
 
 	:::image type="content" source="media/reports-boards/bug-trends-selections.png" alt-text="Screenshot of Power BI Visualizations and Fields selections for Bug trends report. ":::
 
-1. Add the field "**DateValue**" to **X-axis**.
-	- Right-click **DateValue** and select **DateValue**, rather than **Date Hierarchy**.  
+1. Add  `DateValue`" to **X-axis**, and right-click `DateValue` and select `DateValue` rather than `Date Hierarchy`.  
 
-1. Add the field Count to **Y-axis**.
-	- Right-click **Count** and ensure **Sum** is selected.
+1. Add `Count` to **Y-axis**, and right-click `Count` and ensure **Sum** is selected.
 
-1. Add the State to **Legend**.
+1. Add `State` to **Legend**.
 
 The example report displays.  
 
-:::image type="content" source="media/odatapowerbi-bugtrend-report.png" alt-text="Screenshot of Sample Bug trends line chart report.":::
+:::image type="content" source="media/reports-boards/bug-trends-report.png" alt-text="Screenshot of Sample Bug trends line chart report.":::
 
 ### Modify report format visuals 
 
 - To modify format elements of the report, choose the **Format your visual** (paintbrush) icon and modify one or more available settings. For example, you can modify the line colors used in the trend chart.
 
 	:::image type="content" source="media/reports-boards/bug-trends-change-color.png" alt-text="Screenshot of Power BI Format visual selections for Bug trends report. "::: 
 
-To learn more, see [Get started with the formatting pane](/power-bi/visuals/service-getting-started-with-color-formatting-and-axis-properties)
+To learn more, see [Get started with the formatting pane](/power-bi/visuals/service-getting-started-with-color-formatting-and-axis-properties). 
 
 
 ## Related articles

docs/report/powerbi/media/reports-boards/feature-progress-stacked-bar-chart.png

@@ -81,7 +81,7 @@ https://analytics.dev.azure.com/{organization}/{project}/_odata/V3.0-preview/Wor
 - `{organization}` - Your organization name 
 - `{project}` - Your team project name, or omit "/{project}" entirely, for a cross-project query
 * `{teamname}` - The name of the team to display CFD data
-* `{startdate}` - The date to start the CFD chart from. Format: YYYY-MM-DDZ. Example: `2019-04-01Z` represents 2019-April-01. Don't enclose in quotes.
+- `{startdate}` - Start your report for items completed on or after a given date with the format: `YYYY-MM-DDZ`. For example: `2022-04-01Z` represents 2022-April-01. Don't enclose in quotes.
 
 
 ### Query breakdown
@@ -191,23 +191,23 @@ In the follow example, the query was renamed to *CFD*, but no columns were renam
 1. Add `DateValue` to **Axis** and then right-click `DateValue` and select `DateValue`, rather than `Date Hierarchy`.
 
 1. Add `Count` to **Values**.
-2. 
+
 1. Add `ColumnName` to **Legend**.
 
-1. In the Filters pane, expand `ColumnName`, and select only the values you want to appear on the chart. For example, you may want to unselect *New*, *Proposed*, *Done*, or *Closed*.  
+1. In the **Filters** pane, expand `ColumnName`, and select only the values you want to appear on the chart. For example, you may want to unselect *New*, *Proposed*, *Done*, or *Closed*. 
 
 	:::image type="content" source="media/reports-boards/cfd-columnname-filters.png" alt-text="Screenshot of Power BI Filters for ColumnName. ":::
 
 
-The example report displays the columns in alphabetic order. 
+The example report displays the columns in alphabetic order. However, the preferred order is to sort the data according to the Kanban column order, or progressive order. 
 
 :::image type="content" source="media/reports-boards/cfd-stacked-area-chart.png" alt-text="Screenshot of Sample Power BI Cumulative Flow stacked area chart report, columns sorted in alphabetic order.":::
 
 ### Sort columns in progressive order
 
-To sort the chart columns in the order specific on the board, do the following steps:
+To sort the chart columns in the order specific on the Kanban board, do the following steps:
 
-1. Use the query below to create a new query in Power BI. When done, rename the query to *ColumnOrder*. 
+1. Create a new query in Power BI per the following queries. When done, rename the query to *ColumnOrder*. 
 
 #### [Power BI query](#tab/powerbi/)
 
@@ -249,7 +249,7 @@ https://analytics.dev.azure.com/{organization}/{project}/_odata/V3.0-preview/Boa
 1. Select **Column Tools** and then **Sort by Column** and choose `ColumnOrder`.
 	:::image type="content" source="media/reports-boards/cfd-sort-by-column.png" alt-text="Screenshot of Power BI Column Tools, Sort by Column selection.":::
 
-1. Select the **Modeling** menu, and then select **Manage Relationships**. Ensure there's a relationship between `CFD.ColumnName` and `ColumnOrder.ColumnName`. It's likely that the relationship was autodetected.
+1. Select the **Modeling** menu, and then **Manage Relationships**. Ensure there's a relationship between `CFD.ColumnName` and `ColumnOrder.ColumnName`. It's likely that the relationship was autodetected.
 
 	:::image type="content" source="media/reports-boards/cfd-manage-relationships-dialog.png" alt-text="Dialog for Manage Relationships showing a relationship between CFD.ColumnName and ColumnOrder.ColumnName":::