update to quick reference, update cross-links

KathrynEE · KathrynEE · commit 4445e41e3796 · 2022-08-16T15:50:22.000-07:00
AB#1943486: Sample reports and quick reference index
diff --git a/docs/report/analytics/analytics-best-practices.md b/docs/report/analytics/analytics-best-practices.md
@@ -34,7 +34,7 @@ There are several reasons to follow best practices when querying Analytics, such
 - Minimize consumption of resources  
 ::: moniker-end
 
-Follow the guidance provided below as you get started. If you are an extension developer, you'll also want to review [Query guidelines for Analytics with OData](../extend-analytics/odata-query-guidelines.md).
+Follow the guidance provided below as you get started. If you are an extension developer, you'll also want to review [OData Analytics query guidelines](../extend-analytics/odata-query-guidelines.md).
 
 
 [!INCLUDE [prerequisites-simple](../includes/analytics-prerequisites-simple.md)]
@@ -45,7 +45,7 @@ Query the Analytics metadata to gain familiarity with the entity types, entity s
 
 In addition, you can review select information from these resources: 
 - [Analytics OData metadata](../extend-analytics/analytics-metadata.md)
-- [Work item properties reference](../powerbi/analytics-fields-reference.md)
+- [Work tracking properties reference](../powerbi/analytics-fields-reference.md)
 
 
 ## Structure your query to return the data you need 
@@ -106,7 +106,7 @@ You specify columns of data to return using the `$select` clause. With customiza
 
 For example, to return the ID, Work Item Type, Title, and State fields for a filtered set of work items, specify the following `$select` clause: `$select=WorkItemId, WorkItemType, Title, State`.  
 
-To lookup the list of properties and their corresponding field names, see [Work item properties reference](../powerbi/analytics-fields-reference.md). 
+To lookup the list of properties and their corresponding field names, see [Work tracking properties reference](../powerbi/analytics-fields-reference.md). 
 
 <!--- General info 
 Analytics is built on top of a Columnstore Index technology. That means that data is both storage and query processing is column-based. So, the more properties that a query references, the more expensive it's to process. 
@@ -179,7 +179,7 @@ You can review usage for the service and for individuals by going to **Organizat
 - [What is the Analytics service?](../powerbi/what-is-analytics.md)
 - [Query the Analytics service in Azure DevOps](analytics-query-parts.md)
 - [Analytics OData metadata](../extend-analytics/analytics-metadata.md) 
-- [Query guidelines for Analytics with OData](../extend-analytics/odata-query-guidelines.md)
+- [OData Analytics query guidelines](../extend-analytics/odata-query-guidelines.md)
 
 
 
diff --git a/docs/report/analytics/analytics-query-parts.md b/docs/report/analytics/analytics-query-parts.md
@@ -222,7 +222,7 @@ Analytics returns the project names of those projects defined for the *fabrikam*
 ## Related articles
 
 - [What is the Analytics service?](../powerbi/what-is-analytics.md)
-- [Query guidelines for Analytics with OData](../extend-analytics/odata-query-guidelines.md)
+- [OData Analytics query guidelines](../extend-analytics/odata-query-guidelines.md)
 - [Permissions and prerequisites to access Analytics in Azure DevOps](analytics-permissions-prerequisites.md)
 
 <!--- nice to have but not necessary
diff --git a/docs/report/extend-analytics/analytics-metadata.md b/docs/report/extend-analytics/analytics-metadata.md
@@ -231,7 +231,7 @@ Aggregation annotations define the set of [transformations](./odata-supported-fe
 - [Organization and project-scoped queries](account-scoped-queries.md).
 - [Data available from Analytics](../powerbi/data-available-in-analytics.md) 
 - [Query work tracking data using Analytics](analytics-recipes.md)
-- [Work item properties reference](../powerbi/analytics-fields-reference.md) 
+- [Work tracking properties reference](../powerbi/analytics-fields-reference.md) 
 
 
 ## Related resources 
diff --git a/docs/report/extend-analytics/analytics-recipes.md b/docs/report/extend-analytics/analytics-recipes.md
@@ -20,7 +20,7 @@ Analytics. You can adapt most of these queries to meet your needs.
 
 [!INCLUDE [temp](../includes/analytics-preview.md)]
 
-For prerequisites and other information for getting started, see [Query your work tracking data using OData Analytics](wit-analytics.md) and [Work item properties reference](../powerbi/analytics-fields-reference.md). All examples are scoped to a project on Azure DevOps. For examples of organization-level scoping or Azure DevOps Server, see [Project and organization-scoped queries](account-scoped-queries.md). 
+For prerequisites and other information for getting started, see [Query your work tracking data using OData Analytics](wit-analytics.md) and [Work tracking properties reference](../powerbi/analytics-fields-reference.md). All examples are scoped to a project on Azure DevOps. For examples of organization-level scoping or Azure DevOps Server, see [Project and organization-scoped queries](account-scoped-queries.md). 
 
 ::: moniker range="azure-devops"
 > [!TIP] 
@@ -389,4 +389,4 @@ The response returns two work items.
 
 - [WIT analytics](wit-analytics.md)  
 - [Aggregate data](aggregated-data-analytics.md) 
-- [Query guidelines for Analytics with OData](odata-query-guidelines.md)
+- [OData Analytics query guidelines](odata-query-guidelines.md)
diff --git a/docs/report/extend-analytics/data-model-analytics-service.md b/docs/report/extend-analytics/data-model-analytics-service.md
@@ -173,7 +173,7 @@ The following table provides _*a partial list*_ of the **WorkItemRevision** enti
 
 ## Related articles 
 
-- [Query guidelines for Analytics with OData](odata-query-guidelines.md)
+- [OData Analytics query guidelines](odata-query-guidelines.md)
 - [WIT analytics](wit-analytics.md)  
 - [Aggregate data](aggregated-data-analytics.md)
 - [Exploring Analytics OData metadata](analytics-metadata.md)
diff --git a/docs/report/extend-analytics/odata-query-guidelines.md b/docs/report/extend-analytics/odata-query-guidelines.md
@@ -1,16 +1,16 @@
 ---
-title: Query guidelines for Analytics with OData
+title: OData Analytics query guidelines 
 titleSuffix: Azure DevOps
 description: Learn how to write good OData queries that access Analytics for Azure DevOps.
 ms.technology: devops-analytics 
 ms.author: kaelli
 author: KathrynEE
 ms.topic: conceptual
 monikerRange: '>= azure-devops-2019'
-ms.date: 09/30/2020
+ms.date: 08/12/2022
 ---
 
-# Query guidelines for Analytics with OData
+# OData Analytics query guidelines for Azure DevOps
 
 [!INCLUDE [version-gt-eq-2019](../../includes/version-gt-eq-2019.md)]
 
diff --git a/docs/report/extend-analytics/quick-ref.md b/docs/report/extend-analytics/quick-ref.md
@@ -16,22 +16,27 @@ ms.date: 08/12/2022
 [!INCLUDE [version-gt-eq-2019](../../includes/version-gt-eq-2019.md)]
 
 Use this quick reference to access information and sample queries using OData and Analytics.  
-Using OData, you can directly query Analytics for Azure DevOps from a supported browser. Use the returned JSON data as you like. Enterprise organizations generate queries that span multiple projects or the entire organization in Azure DevOps.   
-
-
+Using OData, you can directly query Analytics for Azure DevOps from a supported browser. Use the returned JSON data as you like. Enterprise organizations can generate queries that span multiple projects or an entire organization or project collection.   
 
 ## Get started 
 
+If you're new to Analytics, we recommend that you review the following articles.  
+
+- [Data available and versioning](../powerbi/data-available-in-analytics.md)
 - [Query Analytics data or metadata](../analytics/analytics-query-parts.md)
 - [Supported tools to use with Analytics](../analytics/analytics-query-tools.md)
 - [Summary of best practices to use when querying Analytics](../analytics/analytics-best-practices.md)  
 - [Permissions and prerequisites for working with Analytics](../analytics/analytics-permissions-prerequisites.md) 
 
+ 
+## Sample widgets and reports 
 
+Analytics supports several widgets and built-in reports. In addition, we've created several sample reports to showcase how to query the data and build the reports of interest using Power BI. 
+
+
+[!INCLUDE [temp](../../includes/version-selector-minimize.md)]
 
 
-## Sample reports 
- 
 <!--- include built-in reports and widgets --> 
 
 ::: moniker range=">= azure-devops-2020"
@@ -111,12 +116,27 @@ Using OData, you can directly query Analytics for Azure DevOps from a supported
    :::column-end:::
 :::row-end:::
 ---
---- 
+
 ::: moniker-end
 
 ::: moniker range="azure-devops-2019"
 
-[!INCLUDE [temp](../powerbi/includes/sample-fulllist.md)] 
+For Azure DevOps Server 2019, only Azure Boards work tracking data is available from Analytics. 
+
+- [Bug trend](../powerbi/sample-boards-bugtrend.md) (Power BI)   
+- [Burndown/Burnup](../dashboards/configure-burndown-burnup-widgets.md) (widget)
+- [Cumulative Flow Diagram (CFD)](../dashboards/cumulative-flow.md) (Built-in report, widget)
+- [Cumulative Flow Diagram (CFD)](../powerbi/sample-boards-cfd.md) (Power BI)
+- [Feature progress](../powerbi/sample-boards-featureprogress.md) (Power BI)     
+- [Lead/Cycle Time](../dashboards/cycle-time-and-lead-time.md) (widget)
+- [Lead/Cycle Time](../powerbi/sample-boards-leadcycletime.md) (Power BI)  
+- [Open bugs](../powerbi/sample-boards-openbugs.md) (Power BI)   
+- [Rollup](../powerbi/sample-boards-rollup.md) (Power BI)     
+- [Work items and direct links](../powerbi/sample-boards-directlinks.md) (Power BI)   
+- [Release burndown](../powerbi/sample-boards-releaseburndown.md) (Power BI)
+- [Sprint burndown](../dashboards/configure-sprint-burndown.md) (Built-in report, widget)       
+- [Sprint burndown](../powerbi/sample-boards-sprintburndown.md) (Power BI)    
+- [Velocity](../dashboards/team-velocity.md) (Built-in report, widget) 
 
 ::: moniker-end
 
@@ -235,17 +255,28 @@ Using OData, you can directly query Analytics for Azure DevOps from a supported
 
 ## Reference
 
+- [Work tracking properties reference](../powerbi/analytics-fields-reference.md)  
+- [Analytics views dataset design](../powerbi/data-connector-dataset.md)  
+- [Supported OData functions and clauses](odata-supported-features.md)  
+- [OData API versioning](odata-api-version.md) 
+- [Performance & latency](../powerbi/performance-latency.md)
+
 
 ## Troubleshooting
 
+- [OData Analytics query guidelines for Azure DevOps](odata-query-guidelines.md) 
+- [Resolve errors associated with an Analytics view](../powerbi/troubleshooting-views.md)
+
+## Marketplace extensions
+
+- [WIQL to OData](https://marketplace.visualstudio.com/items?itemName=ms-eswm.wiql-to-odata)
+- [OData for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=stansw.vscode-odata)  
+
 
 ## Related articles
 
 - [Power BI](../powerbi/overview.md)  
 - [Dashboards, charts, reports, & widgets](../dashboards/overview.md)  
 - [OData Extension for Data Aggregation Version 4.0](https://docs.oasis-open.org/odata/odata-data-aggregation-ext/v4.0/cs01/odata-data-aggregation-ext-v4.0-cs01.html)
 
-### Marketplace extensions
 
-- [WIQL to OData](https://marketplace.visualstudio.com/items?itemName=ms-eswm.wiql-to-odata)
-- [OData for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=stansw.vscode-odata)  
diff --git a/docs/report/powerbi/analytics-default-views.md b/docs/report/powerbi/analytics-default-views.md
@@ -64,7 +64,7 @@ Each default Analytics view provides a combination of options for work item type
 
 Default views automatically include the most common fields for the included work item types used for reporting. All custom fields are included. 
 
-For example, the following fields are included when filtered for bugs and user stories. You can look up the description of most of these fields from the [Work item properties reference](analytics-fields-reference.md) or [Work item field index](../../boards/work-items/guidance/work-item-field.md).  
+For example, the following fields are included when filtered for bugs and user stories. You can look up the description of most of these fields from the [Work tracking properties reference](analytics-fields-reference.md) or [Work item field index](../../boards/work-items/guidance/work-item-field.md).  
 
 > [!div class="mx-imgBorder"]
 > ![Analytics views common fields](media/editable-views/common-fields.png)
@@ -84,7 +84,7 @@ In these cases, you can [create a custom Analytics view](analytics-views-create.
 - [Data available from Analytics](data-available-in-analytics.md)
 - [Dataset design for the Power BI Azure DevOps Connector](data-connector-dataset.md)
 - [Grant permissions to access Analytics](./analytics-security.md)
-- [Work item properties reference](analytics-fields-reference.md) 
+- [Work tracking properties reference](analytics-fields-reference.md) 
 
 
 ## Related resources 
diff --git a/docs/report/powerbi/analytics-fields-reference.md b/docs/report/powerbi/analytics-fields-reference.md
@@ -214,7 +214,7 @@ The following surrogate keys (SK) properties can be used to filter or construct
 
 - [About work item fields and attributes](../../boards/work-items/work-item-fields.md)
 - [Index of work item fields](../../boards/work-items/guidance/work-item-field.md) 
-- [Query guidelines for Analytics with OData](../extend-analytics/odata-query-guidelines.md)
+- [OData Analytics query guidelines](../extend-analytics/odata-query-guidelines.md)
 - [Work tracking, process, and project limits](../../organizations/settings/work/object-limits.md) 
 
 
diff --git a/docs/report/powerbi/analytics-historical-filtering.md b/docs/report/powerbi/analytics-historical-filtering.md
@@ -84,5 +84,5 @@ To restate, when reporting on historical data, all filters are applied to the wo
 
 ## Related articles
 
-- [Work item properties reference](analytics-fields-reference.md)
+- [Work tracking properties reference](analytics-fields-reference.md)
 - [Data model for Analytics](../extend-analytics/data-model-analytics-service.md)
diff --git a/docs/report/powerbi/analytics-views-create.md b/docs/report/powerbi/analytics-views-create.md
@@ -74,7 +74,7 @@ Enter a name for the view and provide a description. To allow others to view and
 
 ### Specify Work items filters
 
-Specify filters to reduce the number of results returned by your view. In the work items section, you can add different filters on work item fields to scope your data. For a description of each available field, see [Work item properties reference](analytics-fields-reference.md).
+Specify filters to reduce the number of results returned by your view. In the work items section, you can add different filters on work item fields to scope your data. For a description of each available field, see [Work tracking properties reference](analytics-fields-reference.md).
 > [!div class="mx-imgBorder"]
 > ![Specify Work items filters.](media/editable-views/work-items-default.png)
 
diff --git a/docs/report/powerbi/analytics-views-manage.md b/docs/report/powerbi/analytics-views-manage.md
@@ -104,7 +104,7 @@ To delete a view, select the :::image type="icon" source="../media/icons/actions
 - [Grant permissions to access Analytics](./analytics-security.md)
 - [Power BI integration overview](overview.md)
 - [Query work tracking data using Analytics](../extend-analytics/analytics-recipes.md)
-- [Work item properties reference](analytics-fields-reference.md) 
+- [Work tracking properties reference](analytics-fields-reference.md) 
 
 
 ## Related resources 
diff --git a/docs/report/powerbi/data-connector-dataset.md b/docs/report/powerbi/data-connector-dataset.md
@@ -48,7 +48,7 @@ You can select all work tracking fields in an Analytics view, except for the fol
 > [!IMPORTANT]  
 > Identity or person-name fields, such as Created By, Assigned To, etc., are selectable fields, however you can't select these fields at this time as field criteria for the purposes of filtering work items. 
 
-For a description of each work item tracking fields, see [Work item properties reference](analytics-fields-reference.md).
+For a description of each work item tracking fields, see [Work tracking properties reference](analytics-fields-reference.md).
 
 
 ### Analytics data store fields 
diff --git a/docs/report/powerbi/toc.yml b/docs/report/powerbi/toc.yml
@@ -176,7 +176,7 @@ items:
     href: ../extend-analytics/odata-api-version.md
 - name: Troubleshooting
   items:
-  - name: Query guidelines
+  - name: Odata Analytics query guidelines
     href: ../extend-analytics/odata-query-guidelines.md
   - name: Performance & latency
     href: performance-latency.md
diff --git a/docs/report/powerbi/what-are-analytics-views.md b/docs/report/powerbi/what-are-analytics-views.md
@@ -91,7 +91,7 @@ For more information on how the dataset is modeled when using the Power BI Data
 - [What is Power BI Desktop?](/power-bi/fundamentals/desktop-what-is-desktop) 
 - [Data available from Analytics](data-available-in-analytics.md)
 - [Query work tracking data using Analytics](../extend-analytics/analytics-recipes.md)
-- [Work item properties reference](analytics-fields-reference.md) 
+- [Work tracking properties reference](analytics-fields-reference.md) 
 
 
 ## Related resources 
diff --git a/docs/report/sql-reports/analytics-insights-comparable-sql-reports.md b/docs/report/sql-reports/analytics-insights-comparable-sql-reports.md
@@ -300,7 +300,7 @@ The following table summarizes Analytics reports, widgets, and other tools that
 
 ## Next steps
 > [!div class="nextstepaction"]
-> [Work item properties reference](../powerbi/analytics-fields-reference.md)
+> [Work tracking properties reference](../powerbi/analytics-fields-reference.md)
 
 
 ## Related articles 
diff --git a/docs/report/sql-reports/migration-guide.md b/docs/report/sql-reports/migration-guide.md
@@ -68,7 +68,7 @@ The following tools support interaction with the Analytics service:
 
 ### Query guidelines, query performance and latency 
 
-Analytics is not a real-time time store. It is a curated copy of data stored in Azure DevOps. The data copy helps optimize read and aggregation performance, and reduces the effect reporting scenarios have on Azure DevOps. Copying the data introduces up to a 30-second delay before the data associated with any one change shows up in Analytics. To learn more, see [Query guidelines for Analytics with OData](../extend-analytics/odata-query-guidelines.md).
+Analytics is not a real-time time store. It is a curated copy of data stored in Azure DevOps. The data copy helps optimize read and aggregation performance, and reduces the effect reporting scenarios have on Azure DevOps. Copying the data introduces up to a 30-second delay before the data associated with any one change shows up in Analytics. To learn more, see [OData Analytics query guidelines](../extend-analytics/odata-query-guidelines.md).
 
 
 ### Analytics permissions
