Skip to content

Commit 6587858

Browse files
committed
monikered content
1 parent f7138ab commit 6587858

1 file changed

Lines changed: 79 additions & 22 deletions

File tree

docs/test/request-stakeholder-feedback.md

Lines changed: 79 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -17,31 +17,86 @@ monikerRange: '<= azure-devops'
1717

1818
[!INCLUDE [version-lt-eq-azure-devops](../includes/version-lt-eq-azure-devops.md)]
1919

20-
Use the Test & Feedback extension in Azure DevOps to request, provide, and track stakeholder feedback. Stakeholders can respond to feedback requests or provide voluntary feedback at any time. All feedback is captured in *Feedback Response* work items that you can track with queries.
20+
Use the Test & Feedback extension in Azure DevOps to collect stakeholder feedback. The available workflow depends on your platform:
2121

22-
[!INCLUDE [important-note-request-feedback-unavailable](includes/important-note-request-feedback-unavailable.md)]
22+
- **Azure DevOps Services (cloud):** The formal **Request feedback** action and the extension's **Feedback requests** page aren't available. Stakeholders and Basic users use the extension to capture screenshots, notes, and screen recordings, and then create bugs or tasks.
23+
- **Azure DevOps Server:** The full feedback workflow is available. You can send formal feedback requests from work items, stakeholders respond through the extension's **Provide feedback** flow, and responses are captured in *Feedback Response* work items.
2324

2425
## Prerequisites
2526

2627
| Category | Requirement |
2728
|----------|-------------|
2829
| **Project access** | [Project member](../organizations/security/add-users-team-project.md) |
29-
| **To request feedback** | On Azure DevOps Server, the work-item **Request feedback** action lets users with **Basic** access send requests. In Azure DevOps Services (cloud) this menu action isn't available—use email/chat or the Test & Feedback extension. |
30-
| **To provide feedback** | At least **Stakeholder** access. Basic users can provide feedback using the [nonstakeholder workflow](#non-stakeholder-feedback). |
30+
| **Permissions** | At least **Stakeholder** access. Basic users can also provide feedback. |
3131
| **To track feedback** | Permissions to view and run work item queries. For more information, see [Set query permissions](../boards/queries/set-query-permissions.md). |
3232
| **Extensions** | [Test & Feedback extension](perform-exploratory-tests.md) installed in your browser |
3333

34-
<a name="request"></a>
34+
---
3535

36-
## Request feedback from stakeholders
36+
::: moniker range="azure-devops"
3737

38-
Follow these steps to send a feedback request from a work item:
38+
## Azure DevOps Services (cloud)
3939

40-
1. Open the work item form for the user story or feature you want feedback on.
41-
2. Try to open the shortcut menu (ellipsis …) and select **Request feedback**.
40+
In Azure DevOps Services, the **Request feedback** menu action and the extension's **Feedback requests** page aren't available. To collect stakeholder feedback, ask stakeholders via email or chat to test a feature using the Test & Feedback extension, then create bugs or tasks from their findings.
41+
42+
### Request feedback
43+
44+
Because the built-in **Request feedback** action isn't available in Azure DevOps Services, use one of these alternatives:
45+
46+
- Send an email or chat message to stakeholders with a link to the feature or page to test, along with instructions on what to look for.
47+
- Ask stakeholders to install the [Test & Feedback extension](perform-exploratory-tests.md) and use it to capture and submit bugs or tasks.
48+
49+
### Provide feedback (Azure DevOps Services)
50+
51+
When a stakeholder or Basic user receives a request via email or chat, they use the Test & Feedback extension to capture feedback and create work items.
52+
53+
1. Open the Test & Feedback extension in your browser using the ![launch exploratory testing](media/shared/exp-test-icon.png) icon in the toolbar.
54+
55+
2. In **Connection settings**, select **Connected** mode.
4256

43-
- If the **Request feedback** action is visible, continue with the workflow.
44-
- If you don't see **Request feedback** (expected in Azure DevOps Services/cloud), use [one of the alternatives](#feedback-shortcut-unavailable).
57+
![Screenshot of choosing Connected mode.](media/shared/connectedmode-01.png)
58+
59+
3. Connect to the Azure DevOps organization and project.
60+
61+
![Screenshot showing entering connection details.](media/shared/connectedmode-02.png)
62+
63+
4. Start an exploratory testing session.
64+
65+
![Starting the exploratory testing session](media/voluntary-stakeholder-feedback/voluntary-stakeholder-feedback-26.png)
66+
67+
5. Open the application or web page to test. Use the extension to capture feedback:
68+
- Capture screenshots (with inline annotations)
69+
- Record a short screen capture
70+
- Add notes or steps
71+
72+
![Screenshot of capturing a screenshot.](media/voluntary-stakeholder-feedback/voluntary-stakeholder-feedback-27.png)
73+
74+
Some browsers might not provide all capture capabilities. See [Supported web browsers for the extension](perform-exploratory-tests.md#browser-support).
75+
76+
6. Create a bug or task from the captured information.
77+
78+
![Screenshot shows creating a bug or a task from the captured information.](media/connected-mode-exploratory-testing/create-bugs-02.png)
79+
80+
The process is the same as described in [Exploratory testing in connected mode](connected-mode-exploratory-testing.md#create-bugs).
81+
82+
7. Select the **Stop** icon to end your session.
83+
84+
![Screenshot showing highlighted square icon to stop your feedback session.](media/shared/provide-stakeholder-feedback-12.png)
85+
86+
::: moniker-end
87+
88+
::: moniker range="< azure-devops"
89+
90+
## Azure DevOps Server
91+
92+
Azure DevOps Server supports the full feedback request and response workflow. You can send formal feedback requests from work items, and stakeholders respond through the extension's **Provide feedback** flow. Responses are captured as *Feedback Response* work items.
93+
94+
<a name="request"></a>
95+
96+
### Request feedback from stakeholders
97+
98+
1. Open the work item form for the user story or feature you want feedback on.
99+
2. Open the shortcut menu (ellipsis …) and select **Request feedback**.
45100

46101
3. Enter or select one or more stakeholder names, and optionally add instructions or notes for meaningful feedback.
47102

@@ -53,7 +108,7 @@ Teams can request feedback from other team members, including users with Basic a
53108

54109
<a name="email"></a>
55110

56-
## Provide feedback from a feedback request email
111+
### Provide feedback from a feedback request email
57112

58113
Follow these steps when you receive a Request feedback email.
59114

@@ -67,15 +122,15 @@ Follow these steps when you receive a Request feedback email.
67122

68123
![Screenshot shows confirmation that the extension has been automatically configured.](media/provide-stakeholder-feedback/provide-stakeholder-feedback-05.png)
69124

70-
- If the extension doesn't open or configure automatically, open the extension, sign in, and connect to the organization or project that sent the request.
125+
- If the extension doesn't open or configure automatically, open the extension, sign in, and connect to the server and project that sent the request.
71126

72127
4. Read the instructions in the feedback form to learn what to test and any special notes from the requestor.
73128

74129
![Screenshot shows the feedback form containing the instructions.](media/provide-stakeholder-feedback/provide-stakeholder-feedback-06.png)
75130

76131
5. Depending on your access level:
77-
- Stakeholders: open the **Feedback requests** page in the extension to view and manage any pending requests.
78-
- Basic users: the extension opens the **Explore work item** traceability page that shows the user story, acceptance criteria, and context.
132+
- **Stakeholders:** open the **Feedback requests** page in the extension to view and manage any pending requests.
133+
- **Basic users:** the extension opens the **Explore work item** traceability page that shows the user story, acceptance criteria, and context.
79134

80135
![Screenshot shows the traceability page showing the user story and user acceptance criteria.](media/provide-stakeholder-feedback/provide-stakeholder-feedback-18.png)
81136

@@ -88,8 +143,8 @@ Follow these steps when you receive a Request feedback email.
88143
![Screenshot shows capturing a screenshot.](media/shared/provide-stakeholder-feedback-07.png)
89144

90145
7. Submit your feedback:
91-
- Stakeholders: choose **Provide feedback** in the extension. Optionally create bugs or tasks when you submit.
92-
- Basic users: create a bug or a task from the captured information (nonstakeholder flow).
146+
- **Stakeholders:** choose **Provide feedback** in the extension. Optionally create bugs or tasks when you submit.
147+
- **Basic users:** create a bug or a task from the captured information (nonstakeholder flow).
93148

94149
![Screenshot shows submitting your feedback.](media/shared/provide-stakeholder-feedback-08.png)
95150
![Screenshot shows creating a bug or a task from the captured information.](media/connected-mode-exploratory-testing/create-bugs-02.png)
@@ -110,12 +165,12 @@ Follow these steps when you receive a Request feedback email.
110165

111166
<a name="direct"></a>
112167

113-
## Provide feedback from the Test & Feedback extension
168+
### Provide feedback from the Test & Feedback extension
114169

115170
Use this flow when you want to manage multiple requests or work directly from the extension.
116171

117172
1. Launch the extension from the toolbar icon (![launch exploratory testing](media/shared/exp-test-icon.png)).
118-
2. In Connection settings, select **Connected** mode and sign in to the Azure DevOps organization that hosts the request.
173+
2. In Connection settings, select **Connected** mode and sign in to the Azure DevOps Server instance that hosts the request.
119174
3. Connect to the server and the project or team that requested feedback.
120175

121176
![Screenshot of the Test & Feedback extension connection dialog showing server and project fields for entering connection details.](media/shared/connectedmode-02.png)
@@ -133,9 +188,9 @@ Use this flow when you want to manage multiple requests or work directly from th
133188

134189
<a name="voluntary"></a>
135190

136-
## Provide voluntary feedback
191+
### Provide voluntary feedback
137192

138-
Use the Test & Feedback extension to provide voluntary feedback, even if you don't receive a feedback request.
193+
Use the Test & Feedback extension to provide voluntary feedback on Azure DevOps Server, even if you don't receive a feedback request.
139194

140195
1. Open the Test & Feedback extension in your browser using the ![launch exploratory testing](media/shared/exp-test-icon.png) icon in the toolbar.
141196

@@ -179,10 +234,12 @@ Use the Test & Feedback extension to provide voluntary feedback, even if you don
179234

180235
<a name="non-stakeholder-feedback"></a>
181236

182-
## Nonstakeholder (Basic user) workflow
237+
### Nonstakeholder (Basic user) workflow
183238

184239
If you have Basic access and the requestor invited you to respond, the extension opens the Explore work item view. Use that view to capture details and then create a bug or task from the captured feedback. For full instructions, see [Exploratory testing in connected mode](connected-mode-exploratory-testing.md#create-bugs).
185240

241+
::: moniker-end
242+
186243
<a name="track"></a>
187244

188245
## Track feedback requests

0 commit comments

Comments
 (0)