direct links report article updates

Author: KathrynEE

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

@@ -6,10 +6,7 @@ ms.topic: include
 ms.date: 12/05/2022
 ---
 
-## Query filters
-
-To determine available query filters or properties to return, 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 or return properties using any of the `Property` values under an `EntityType` or `NavigationPropertyBinding Path` values listed under the `EntitySet` you specify for your query. Each `EntitySet` corresponds to an `EntityType`. For example, the `EntitySet Name="WorkItemSnapshot"` corresponds to the `EntityType Name="WorkItemSnapshot"`.
-
-To learn more about the data type of each value, review the metadata provided for the corresponding `EntityType`.  
+> [!NOTE]   
+> To determine available properties for filter or report purposes, see [Metadata reference for Azure Boards](../../analytics/entity-reference-boards).  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/includes/sample-full-list-pipelines.md

@@ -8,16 +8,16 @@ ms.date: 08/14/2020
 
 
 :::row:::
-   :::column span="2":::
+   :::column span="1":::
       **Pipeline**
    :::column-end:::
-   :::column span="2":::
+   :::column span="1":::
       **Pipeline and test** 
    :::column-end:::
 :::row-end:::
 ---
 :::row:::
-   :::column span="2":::
+   :::column span="1":::
       - [Outcome summary](../sample-pipelines-outcome-summary.md)
       - [Outcome summary for all pipelines](../sample-pipelines-allpipelines.md)
       - [Pass rate trend](../sample-pipelines-pass-rate-trend.md)  
@@ -27,7 +27,7 @@ ms.date: 08/14/2020
       - [Task duration](../sample-pipelines-task-duration.md)  
       - [Task duration trend](../sample-pipelines-task-duration-trend.md)  
    :::column-end:::
-   :::column span="2":::
+   :::column span="1":::
       - [Test summary](../sample-test-analytics-test-summary.md) 
       - [Test summary trend](../sample-test-summary-trend.md) 
       - [Failed tests](../sample-test-analytics-failed-tests.md) 

docs/report/powerbi/media/reports-boards/parent-child-links-list-table-visualizations.png

@@ -29,7 +29,9 @@ This article shows you how to display, for a given set of open Bugs, the number
 
 ## Sample queries
 
-The following queries return data from the `WorkItemSnapshot` entity set to support generating trend reports.  
+The following queries return data from the `WorkItemSnapshot` entity set to support generating trend reports. 
+
+[!INCLUDE [temp](includes/query-filters-work-items.md)]  
 
 ### Bug trend filtered by Area Path
 
@@ -91,90 +93,90 @@ https://analytics.dev.azure.com/{organization}/{project}/_odata/v3.0-preview/Wor
 The following table describes each part of the query.  
 
 :::row:::
-   :::column span="2":::
+   :::column span="1":::
    **Query part**
    :::column-end:::
-   :::column span="2":::
+   :::column span="1":::
    **Description**
    :::column-end:::
 :::row-end:::
 :::row:::
-   :::column span="2":::
+   :::column span="1":::
    `$apply=filter(`
    :::column-end:::
-   :::column span="2":::
+   :::column span="1":::
    Start of filter statement clause.
    :::column-end:::
 :::row-end:::
 :::row:::
-   :::column span="2":::
+   :::column span="1":::
    `WorkItemType eq 'Bug'`
    :::column-end:::
-   :::column span="2":::
+   :::column span="1":::
    Return Bugs.
    :::column-end:::
 :::row-end:::
 :::row:::
-   :::column span="2":::
+   :::column span="1":::
    `and State ne 'Closed'`
    :::column-end:::
-   :::column span="2":::
+   :::column span="1":::
    Omit bugs in a Closed state.
    :::column-end:::
 :::row-end:::
 :::row:::
-   :::column span="2":::
+   :::column span="1":::
    `and startswith(Area/AreaPath,'{areapath}')`
    :::column-end:::
-   :::column span="2":::
+   :::column span="1":::
   Filter work items under a specific **Area Path** that you specify in`'{areapath}'`.<br>To filter by team name, use the filter statement `Teams/any(x:x/TeamName eq '{teamname})'`.
    :::column-end:::
 :::row-end:::
 :::row:::
-   :::column span="2":::
+   :::column span="1":::
    `and DateValue ge {startdate}`
    :::column-end:::
-   :::column span="3":::
+   :::column span="1":::
    Start trend on or after the specified date. Example: **2021-04-01Z** represents 2021-April-01.
    :::column-end:::
 :::row-end:::
 :::row:::
-   :::column span="2":::
+   :::column span="1":::
    `)`
    :::column-end:::
-   :::column span="2":::
+   :::column span="1":::
    Close `filter()` clause.
    :::column-end:::
 :::row-end:::
 :::row:::
-   :::column span="2":::
+   :::column span="1":::
    `/groupby(`
    :::column-end:::
-   :::column span="2":::
+   :::column span="1":::
    Start `groupby()` clause.
    :::column-end:::
 :::row-end:::
 :::row:::
-   :::column span="2":::
+   :::column span="1":::
    `(DateValue, State, WorkItemType, Priority, Severity, Area/AreaPath, Iteration/IterationPath), `
    :::column-end:::
-   :::column span="2":::
+   :::column span="1":::
    Group by `DateValue`,  used for trending, and any other fields you want to report on.
    :::column-end:::
 :::row-end:::
 :::row:::
-   :::column span="2":::
+   :::column span="1":::
    `aggregate($count as Count)`
    :::column-end:::
-   :::column span="2":::
+   :::column span="1":::
    Aggregate by counting bugs that match the criteria on each date.
    :::column-end:::
 :::row-end:::
 :::row:::
-   :::column span="2":::
+   :::column span="1":::
    `)`
    :::column-end:::
-   :::column span="2":::
+   :::column span="1":::
    Close `groupby()` clause.
    :::column-end:::
 :::row-end:::