You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
title: Add an Action | Extensions for Azure DevOps
5
-
description: Add an action for your extension that extends Azure DevOps.
3
+
ms.custom: devx-track-js, UpdateFrequency3
4
+
title: Add a menu action
5
+
titleSuffix: Azure DevOps
6
+
description: Add a context menu action to your Azure DevOps extension.
6
7
ms.assetid: 7b117bbf-f188-41ce-8ff6-3723ebccea81
7
8
ms.topic: how-to
8
9
monikerRange: '<= azure-devops'
9
10
ms.author: chcomley
10
11
author: chcomley
11
-
ms.date: 08/22/2016
12
+
ms.date: 04/03/2026
13
+
ai-usage: ai-assisted
12
14
---
13
15
14
16
# 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
24
26
-[Develop a web extension](../get-started/node.md).
25
27
-[Create a web app for your action](./add-hub.md).
26
28
27
-
## Update extension manifest file
29
+
## Update the extension manifest
28
30
29
-
Below is the code snippet that adds your action to the contributions section of your [extension manifest](../develop/manifest.md).
31
+
Add your action to the contributions section of your [extension manifest](../develop/manifest.md).
30
32
```json
31
33
...
32
34
"contributions": [
@@ -63,59 +65,49 @@ Learn about all of the places where you can add actions in [Extensibility points
63
65
64
66
## Your HTML page
65
67
66
-
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
67
-
in your extension's manifest file.
68
+
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.
68
69
69
70
```html
70
-
<!DOCTYPE html>
71
-
<htmllang="en">
72
-
<head>
73
-
<metacharset="UTF-8">
74
-
<title>Action Sample</title>
75
-
</head>
76
-
<body>
77
-
<div>
78
-
The end user doesn't see the content on this page.
79
-
It is only in the background to handle the contributed menu item being selected.
80
-
</div>
81
-
</body>
82
-
</html>
83
-
```
84
-
85
-
## Your JavaScript
86
-
The script below registers the handler object to handle the action, place it in the `head` section of the previous HTML page.
87
-
88
-
> We aliased `lib` to be `node_modules/azure-devops-extension-sdk/lib` in our `sdk-extension.json` manifest file.
89
-
90
-
```typescript
91
-
<scriptsrc="lib/SDK.min.js"></script>
92
-
<script>
93
-
SDK.init();
94
-
95
-
// Use an IIFE to create an object that satisfies the IContributedMenuSource contract
96
-
var menuContributionHandler = (function () {
97
-
"use strict";
98
-
return {
99
-
// This is a callback that gets invoked when a user selects the newly contributed menu item
100
-
// The actionContext parameter contains context data surrounding the circumstances of this
title: Add panels on backlog pages | Extensions for Azure DevOps Services
3
-
description: Extend Azure DevOps Services with panels on backlogs.
2
+
title: Add Panels to Azure DevOps Backlog Pages
3
+
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.

23
-
-->
24
+

24
25
25
-

26
+
The custom panel opens in the same space as the mapping panel.
26
27
27
-
The custom panel opens in the same space that the mapping panel opens if it were selected.
28
+

28
29
29
-

30
+
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.
30
31
31
-
32
-
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.
0 commit comments