Merge pull request #9099 from MicrosoftDocs/main

Auto Publish – main to live - 2026-04-03 21:00 UTC

Author: learn-build-service-prod[bot]

.openpublishing.redirection.json

@@ -1440,6 +1440,14 @@
         "azure-devops-2020"
       ]
     },
+    {
+      "source_path": "docs/extend/develop/add-hub-group.md",
+      "redirect_url": "/azure/devops/extend/develop/add-hub#add-a-custom-hub-group",
+      "redirect_document_id": false,
+      "monikers": [
+        "azure-devops"
+      ]
+    },
     {
       "source_path": "docs/extend/develop/add-query-result-tabs.md",
       "redirect_url": "/previous-versions/azure/devops/extend/develop/add-query-result-tabs",
@@ -1522,12 +1530,20 @@
     },
     {
       "source_path": "docs/extend/develop/host-navigation.md",
-      "redirect_url": "/previous-versions/azure/devops/extend/develop/host-navigation",
+      "redirect_url": "/azure/devops/extend/develop/work-with-urls",
       "redirect_document_id": false,
       "monikers": [
         "azure-devops-2020"
       ]
     },
+    {
+      "source_path": "docs/extend/develop/host-navigation.md",
+      "redirect_url": "/azure/devops/extend/develop/work-with-urls",
+      "redirect_document_id": false,
+      "monikers": [
+        "azure-devops"
+      ]
+    },
     {
       "source_path": "docs/extend/develop/integrate-build-task.md",
       "redirect_url": "/previous-versions/azure/devops/extend/develop/integrate-build-task",
@@ -8706,7 +8722,7 @@
     },
     {
       "source_path": "docs/extend/develop/host-navigation.md",
-      "redirect_url": "/previous-versions/azure/devops/extend/develop/host-navigation",
+      "redirect_url": "/azure/devops/extend/develop/work-with-urls",
       "redirect_document_id": false,
       "monikers": [
         "azure-devops-2019"
@@ -14472,6 +14488,21 @@
       "source_path_from_root": "/docs/pipelines/test/codecoverage-for-pullrequests.md",
       "redirect_url": "/azure/devops/pipelines/test/review-code-coverage-results",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/test/provide-stakeholder-feedback.md",
+      "redirect_url": "/azure/devops/test/request-stakeholder-feedback",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "docs/test/voluntary-stakeholder-feedback.md",
+      "redirect_url": "/azure/devops/test/request-stakeholder-feedback",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/test/track-stakeholder-feedback.md",
+      "redirect_url": "/azure/devops/test/request-stakeholder-feedback",
+      "redirect_document_id": false
     }
   ]
 }

docs/cross-service/cross-service-overview.md

@@ -123,7 +123,7 @@ Several collaboration scenarios are supported through Azure Boards work item typ
 | Request code review | **Code Review Request** | Tracks information entered into the TFVC New Code Review form. For more information, see [Get your code reviewed with Visual Studio](../repos/tfvc/get-code-reviewed-vs.md). |
 | Provide code review | **Code Review Response** | Tracks review comments provided by code reviewers in [response to a code review request](../repos/tfvc/get-code-reviewed-vs.md#respond-to-the-code-review-request). |
 | Request feedback | **Feedback Request** | Tracks information entered into a request feedback form. Use the following forms to initiate a feedback request. <br> - [Request stakeholder feedback](../test/request-stakeholder-feedback.md) <br> - [Get feedback](/previous-versions/azure/devops/project/feedback/get-feedback). |
-| Provide feedback | **Feedback Review** | Lets stakeholders [provide feedback](../test/provide-stakeholder-feedback.md) based on requests for feedback or by [volunteering feedback](../test/voluntary-stakeholder-feedback.md) using the [Microsoft Test & Feedback](https://marketplace.visualstudio.com/items?itemName=ms.vss-exploratorytesting-web) Marketplace extension. |
+| Provide feedback | **Feedback Review** | Lets stakeholders [provide feedback](../test/request-stakeholder-feedback.md#email) based on requests for feedback or by [volunteering feedback](../test/request-stakeholder-feedback.md#voluntary) using the [Microsoft Test & Feedback](https://marketplace.visualstudio.com/items?itemName=ms.vss-exploratorytesting-web) Marketplace extension. |
 | Manual testing | **Test Plan** | Groups one or more test suites and individual test cases together. Test plans include static test suites, requirement-based suites, and query-based suites. To get started, see [Create test plans and test suites](../test/create-a-test-plan.md). |
 | Manual testing | **Test Suite** | Groups one or more test cases into separate testing scenarios within a single test plan. Grouping test cases makes it easier to see which scenarios are complete. |
 | Manual testing | **Test Case** | Defines steps used to validate individual parts of your code to ensure your code works correctly, has no errors, and meets business and customer requirements. You can [add individual test cases](../test/create-test-cases.md) to a test plan without creating a test suite. More than one test suite or test plan can refer to a test case. You can effectively reuse test cases without having to copy or clone them for each suite or plan. |

docs/extend/develop/add-action.md

@@ -1,14 +1,16 @@
 ---
 ms.subservice: azure-devops-ecosystem
-ms.custom: devx-track-js
-title: Add an Action | Extensions for Azure DevOps
-description: Add an action for your extension that extends Azure DevOps.
+ms.custom: devx-track-js, UpdateFrequency3
+title: Add a menu action
+titleSuffix: Azure DevOps
+description: Add a context menu action to your Azure DevOps extension.
 ms.assetid: 7b117bbf-f188-41ce-8ff6-3723ebccea81
 ms.topic: how-to
 monikerRange: '<= azure-devops'
 ms.author: chcomley
 author: chcomley
-ms.date: 08/22/2016
+ms.date: 04/03/2026
+ai-usage: ai-assisted
 ---
 
 # Add a menu action
@@ -24,9 +26,9 @@ In this example, we add an action to the query context menu in the work item que
 - [Develop a web extension](../get-started/node.md).
 - [Create a web app for your action](./add-hub.md).
 
-## Update extension manifest file
+## Update the extension manifest
 
-Below is the code snippet that adds your action to the contributions section of your [extension manifest](../develop/manifest.md).
+Add your action to the contributions section of your [extension manifest](../develop/manifest.md).
 ```json
 ...
     "contributions": [
@@ -63,59 +65,49 @@ Learn about all of the places where you can add actions in [Extensibility points
 
 ## Your HTML page
 
-Your menu action is represented by a JavaScript script embedded in an HTML file. Save the following contents in a file and location that matches the reference to it 
-in your extension's manifest file.
+Your menu action is represented by a JavaScript script embedded in an HTML file. Save the following contents in a file and location that matches the reference to it in your extension's manifest file.
 
 ```html
-	<!DOCTYPE html>
-	<html lang="en">
-	<head>
-		<meta charset="UTF-8">
-		<title>Action Sample</title>
-	</head>
-	<body>
-		<div>
-			The end user doesn't see the content on this page.
-			It is only in the background to handle the contributed menu item being selected.
-		</div>
-	</body>
-	</html>
-```
-
-## Your JavaScript
-The script below registers the handler object to handle the action, place it in the `head` section of the previous HTML page.
-
-> We aliased `lib` to be `node_modules/azure-devops-extension-sdk/lib` in our `sdk-extension.json` manifest file.
-
-```typescript
-<script src="lib/SDK.min.js"></script>
-<script>
-    SDK.init();
-
-    // Use an IIFE to create an object that satisfies the IContributedMenuSource contract
-    var menuContributionHandler = (function () {
-        "use strict";
-        return {
-            // This is a callback that gets invoked when a user selects the newly contributed menu item
-            // The actionContext parameter contains context data surrounding the circumstances of this
-            // action getting invoked.
-            execute: function (actionContext) {
-                alert("Hello, world");
+<!DOCTYPE html>
+<html lang="en">
+<head>
+    <meta charset="UTF-8">
+    <title>Action Sample</title>
+    <script src="https://cdnjs.cloudflare.com/ajax/libs/require.js/2.3.6/require.min.js"></script>
+    <script>
+        window.requirejs.config({
+            enforceDefine: true,
+            paths: {
+                'SDK': './lib/SDK.min'
             }
-        };
-    }());
-
-    // Associate the menuContributionHandler object with the "myAction" menu contribution from the manifest.
-    SDK.register(SDK.getContributionId(), menuContributionHandler);
-</script>
+        });
+        window.requirejs(['SDK'], function (SDK) {
+            SDK.init();
+            SDK.ready().then(() => {
+                // Register the menu action handler
+                SDK.register(SDK.getContributionId(), {
+                    execute: function (actionContext) {
+                        alert("Hello, world");
+                    }
+                });
+            });
+        });
+    </script>
+</head>
+<body>
+    <div>
+        The end user doesn't see the content on this page.
+        It runs in the background to handle the contributed menu item being selected.
+    </div>
+</body>
+</html>
 ```
 
 [!INCLUDE [tip-for-more-information](../includes/tip-for-more-information.md)]
 
 ## Next steps
 
-Now that you've written your extension, the next steps are to Package, Publish, and Install your extension. You can also check out the 
-documentation for Testing and Debugging your extension. 
+Package, publish, and install your extension.
 
 * [Package, publish, and install extensions](../publish/overview.md)
 * [Testing and debugging extensions](/previous-versions/azure/devops/extend/test/debug-in-browser)

docs/extend/develop/add-backlog-panel.md

@@ -1,38 +1,35 @@
 ---
-title: Add panels on backlog pages | Extensions for Azure DevOps Services
-description: Extend Azure DevOps Services with panels on backlogs.
+title: Add Panels to Azure DevOps Backlog Pages
+description: Add panels on backlog pages in Azure DevOps to enhance your workflow. Learn how to extend backlogs with custom panels and streamline project management.
 ms.assetid: 34f01da42-5a98-4bc5-981e-3f8d1ffdf163
 ms.subservice: azure-devops-ecosystem
 ms.topic: how-to
+ms.custom: UpdateFrequency3
 monikerRange: 'azure-devops'
 ms.author: chcomley
+ms.reviewer: chcomley
 author: chcomley
-ms.date: 02/21/2025
+ms.date: 04/03/2026
+ai-usage: ai-assisted
 ---
 
 # Add panels on backlog pages
 
 [!INCLUDE [version-eq-azure-devops](../../includes/version-eq-azure-devops.md)]
 
-Here, we add a simple Hello World extension as a panel on the Portfolio backlog, Product backlog, and Iteration backlog.
+This article shows how to add a custom panel to the Portfolio backlog, Product backlog, and Iteration backlog pages.
 
 [!INCLUDE [extension-docs-new-sdk](../../includes/extension-docs-new-sdk.md)]
 
-<!---
-![panel extension on the Azure DevOps Services Portfolio backlog page](../media/backlog-pane/portfolio-backlog-pane.png)
--->
+![Screenshot of open panel extension on the Stories backlog page.](media/add-panel-intro-show-mapping-hello-world.png)
 
-![Open panel extension on the Azure DevOps Services Stories backlog page](media/add-panel-intro-show-mapping-hello-world.png)
+The custom panel opens in the same space as the mapping panel.
 
-The custom panel opens in the same space that the mapping panel opens if it were selected.  
+![Screenshot of custom panel extension on the Portfolio backlog page.](media/add-panel-show-custom-panel.png)
 
-![panel extension on the Azure DevOps Services Portfolio backlog page](media/add-panel-show-custom-panel.png)
+Three backlog categories support panel extensions. The following contribution points apply to Agile, Scrum, and CMMI process templates. For custom templates, check your process to identify which backlogs use the requirement or portfolio category.
 
-
-There are three types of backlogs that can be targets for panel extensions: Portfolio backlogs, Product backlogs, and Iteration backlogs. For the Agile template, this breakdown is as below. This is representative of Scrum and CMMI as well. For custom templates, please consult your process to see which backlogs are requirement or portfolio category. 
-
-
-| Backlog Category   | Contribution point |
+| Backlog category   | Contribution point |
 |--------------------|--------------------|
 | Portfolio (Epic, Feature) | ms.vss-work-web.portfolio-backlog-toolpane |
 | Requirements (User Story, Product Backlog Item) | ms.vss-work-web.requirement-backlog-toolpane | 
@@ -42,10 +39,10 @@ For more information, see the [Azure DevOps Services Extension Sample](https://g
 
 ## Update your extension manifest
 
-Update your [extension manifest](../develop/manifest.md) file with the following code:
+Update your [extension manifest](manifest.md) file with the following code. This example adds a panel to all three backlog types.
 
 ```json
-...
+{
 	"contributions": [
 		{
 			"id": "Fabrikam.HelloWorld.Backlogs.Panel",
@@ -64,37 +61,38 @@ Update your [extension manifest](../develop/manifest.md) file with the following
 			}
 		}
 	],
-	"scopes": [ 
-		"vso.work" 
+	"scopes": [
+		"vso.work"
 	]
-... 
+}
 ```
 
 ### Contribution
-For each contribution in your extension, the manifest defines
-* the type of contribution (backlog panel in this case),
-* the contribution target (the requirements, portfolio, and iteration backlogs in this case),
-* and the properties that are specific to each type of contribution. For panels, we have
 
+For each contribution in your extension, the manifest defines:
 
-| Property           | Description                                                                                                                         
-|--------------------|----------------------------------------------------------------------------------------|                
-| title              | Tooltip text that appears on the menu item                                        |                   
-| name               | What appears in the dropdown for panel selection					                  |                   
-| uri                | Path (relative to the extension's base URI) of the page to surface as the panel     |                   
-| registeredObjectId | ID of the object registered for the panel                                             |    
+- The type of contribution, such as `backlog-panel`
+- The contribution targets, such as the requirement, portfolio, and iteration backlog toolpanes
+- The properties specific to each contribution type
 
+The following table describes the panel-specific properties.
 
-Learn about all of the places where you can add an extension in [Extensibility points](../reference/targets/overview.md).
+| Property | Description |
+|---|---|
+| `title` | Tooltip text that appears on the menu item. |
+| `name` | Text that appears in the dropdown for panel selection. |
+| `uri` | Path, relative to the extension's base URI, of the page to surface as the panel. |
+| `registeredObjectId` | ID of the object registered for the panel. |
 
-### Scopes
-Include the [scopes](manifest.md#scopes) that your extension requires.
-In this case, we need `vso.work` to access work items.
+For more information about where you can add an extension, see [Extensibility points](../reference/targets/overview.md).
 
+### Scopes
 
+Include the [scopes](manifest.md#scopes) that your extension requires. This example uses `vso.work` to access work items.
 
 ## Get selection events
-To get selection events (information about what work items are selected) implement this interface on your registered object.
+
+To get selection events about which work items are selected, implement this interface on your registered object.
 
 ```javascript
 ...
@@ -104,10 +102,7 @@ To get selection events (information about what work items are selected) impleme
 ...
 ```
 
-## Next steps
+## Next step
 
 > [!div class="nextstepaction"]
 > [Package, Publish, and Install](../publish/overview.md)
-or
-> [!div class="nextstepaction"]
-> [Test and Debug](/previous-versions/azure/devops/extend/test/debug-in-browser)

docs/extend/develop/add-backlog-tabs.md

@@ -1,13 +1,16 @@
 ---
-title: Add tabs on backlog pages | Extensions for Azure DevOps Services
-description: Learn how to create a web page in an iframe, and host it in Azure DevOps Services as a tab on the backlog pages.
+title: Add tabs on backlog pages
+titleSuffix: Azure DevOps
+description: Add custom tabs to product and iteration backlog pages in your Azure DevOps extension.
 ms.assetid: 3D0B51DA-66AA-45C7-B9F1-08973CFF7E5E
 ms.subservice: azure-devops-ecosystem
+ms.custom: UpdateFrequency3
 ms.topic: how-to
 monikerRange: 'azure-devops'
 ms.author: chcomley
 author: chcomley
-ms.date: 03/21/2019
+ms.date: 04/03/2026
+ai-usage: ai-assisted
 ---
 
 # Add tabs on backlog pages
@@ -93,7 +96,7 @@ In this case, we need `vso.work` to access work items.
 Include all of the files your extension accesses. <br>
 For your files, set `addressable` to `true` unless you include other files that don't need to be URL-addressable.
 
-## Example registeredObjectId
+## Register the tab object
 ```javascript
 SDK.register("backlogTabObject", {
     pageTitle: function(state) {