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
Copy file name to clipboardexpand all lines: docs/boards/backlogs/configure-your-backlog-view.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -190,7 +190,7 @@ If your team follows Agile or Scrum methods, they'll want to prioritize the back
190
190
To reorder a backlog, you must have **Basic** or higher level access. If you have Stakeholder access, you can't reorder backlog items. For more information, see [Stakeholder access quick reference](../../organizations/security/stakeholder-access.md).
191
191
192
192
> [!NOTE]
193
-
> Changes you make to the priority impact all backlog items. When other team members refresh their backlog, they'll see the new priorities. A background process updates the [**Stack Rank** (Agile, Basic, and CMMI processes)](../queries/planning-ranking-priorities.md) or [**Backlog Priority** (Scrum process)](../queries/planning-ranking-priorities.md) fields. These fields are used by the system to track the relative ranking of items on the product, feature, epic, or other portfolio backlog. By default, these fields don't appear on the work item form. The priority ranking is assigned separately to each backlog level, which you can check by adding the field to a backlog and viewing a hiearchical list.
193
+
> Changes you make to the priority impact all backlog items. When other team members refresh their backlog, they'll see the new priorities. A background process updates the [**Stack Rank** (Agile, Basic, and CMMI processes)](../queries/planning-ranking-priorities.md) or [**Backlog Priority** (Scrum process)](../queries/planning-ranking-priorities.md) fields. These fields are used by the system to track the relative ranking of items on the product, feature, epic, or other portfolio backlog. By default, these fields don't appear on the work item form. The priority ranking is assigned separately to each backlog level, which you can check by adding the field to a backlog and viewing a hierarchical list.
194
194
195
195
Backlogs that participate in portfolio management or that contain nested same-type child items might not allow you to reorder the items. For more information, see these articles:
196
196
-[Backlogs, portfolios, and Agile project management, Work with multi-team ownership of backlog items](backlogs-overview.md#multi-team)
The deleted attachment cannot be restored and is permenantly removed after 28 days. In the meantime, if you have permissions, you can [permanently delete](#permanently-delete-attachments) it.
246
+
The deleted attachment cannot be restored and is permanently removed after 28 days. In the meantime, if you have permissions, you can [permanently delete](#permanently-delete-attachments) it.
Copy file name to clipboardexpand all lines: docs/boards/queries/query-operators-variables.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -551,7 +551,7 @@ For more information, see [Define a query](using-queries.md).
551
551
552
552
553
553
> [!TIP]
554
-
> It's possible to contsruct a query using WIQL syntax that uses an operator, such as **Was Ever**, for other data type fields than those listed. For example, you can use **Was Ever** within a clause using the **Iteration Path**. For an example, see [Query by date or current iteration, List work items moved out of a sprint](query-by-date-or-current-iteration.md#list-work-items-moved-out-sprint).
554
+
> It's possible to construct a query using WIQL syntax that uses an operator, such as **Was Ever**, for other data type fields than those listed. For example, you can use **Was Ever** within a clause using the **Iteration Path**. For an example, see [Query by date or current iteration, List work items moved out of a sprint](query-by-date-or-current-iteration.md#list-work-items-moved-out-sprint).
Copy file name to clipboardexpand all lines: docs/extend/develop/service-endpoints.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -234,7 +234,7 @@ Create a `task.json` file in your `BuildTaskFolder` directory, if you haven't cr
234
234
"label": "Fabrikam service/server end point",
235
235
"defaultValue": "",
236
236
"required": true,
237
-
"helpMarkDown": "Select the Fabrikam end point to use. If needed,selecton 'manage', and add a new service endpoint of type 'Fabrikam server connection'"
237
+
"helpMarkDown": "Select the Fabrikam end point to use. If needed,select 'manage', and add a new service endpoint of type 'Fabrikam server connection'"
Copy file name to clipboardexpand all lines: docs/extend/develop/using-host-dialog.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -117,7 +117,7 @@ The `uri` property references a page that is rendered within the content area of
117
117
118
118
### Showing the dialog
119
119
120
-
To show the dialog (for example, when a user selects an action on a toolbar or menu), call the `openDialog` function on an instance of the HostDialogService, passing the fully-qualified identifer of the dialog content, for example `my-publisher.my-extension.registration-form` and any dialog options:
120
+
To show the dialog (for example, when a user selects an action on a toolbar or menu), call the `openDialog` function on an instance of the HostDialogService, passing the fully-qualified identifier of the dialog content, for example `my-publisher.my-extension.registration-form` and any dialog options:
Copy file name to clipboardexpand all lines: docs/includes/features-not-available-stakeholder.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ ms.date: 04/04/2022
11
11
If a Stakeholder needs access to one or more of the following features—which support the daily work of product owners, team leads, developers, testers, and project administrators—you need to provide them **Basic** access.
12
12
13
13
> [!NOTE]
14
-
> Even if Stakeholders are explicity granted permissions to some features, they are disallowed access to the feature due to their access level. Stakeholders that choose a feature that's not available to them receive an error message indicating that they don't have permissions to complete the task.
14
+
> Even if Stakeholders are explicitly granted permissions to some features, they are disallowed access to the feature due to their access level. Stakeholders that choose a feature that's not available to them receive an error message indicating that they don't have permissions to complete the task.
Copy file name to clipboardexpand all lines: docs/managed-devops-pools/configure-scaling.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -235,7 +235,7 @@ Manual mode is best suited for teams that have knowledge of their CI/CD pipeline
235
235
You can create your own provisioning schedule or choose from one of the predefined schedules, and you can configure the time zone to use for specifying the schedules. The default value for **Pre-provisioning TimeZone** is **(UTC) Coordinated Universal Time**.
236
236
237
237
> [!TIP]
238
-
> The provisioning count in a scheme can't be greater than the **Maximim agents** configured in [Pool settings](configure-pool-settings.md#maximum-agents).
238
+
> The provisioning count in a scheme can't be greater than the **Maximum agents** configured in [Pool settings](configure-pool-settings.md#maximum-agents).
239
239
240
240
Every few minutes, Managed DevOps Pools checks the count of active agents running jobs and standby agents waiting for jobs, to ensure that the provisioning count of agents specified by the current provisioning scheme are available. If the current provisioning count is 10, and there are five agents running jobs and two agents on standby, Managed DevOps Pools will start three additional standby agents to bring the total agent count up to 10.
241
241
@@ -349,7 +349,7 @@ A single `daysData` item contains a dictionary of times and standby agent counts
349
349
"daysData": [
350
350
{}, # Schedule of standby agent count adjustments for Sunday
351
351
{ # Schedule of standby agent count adjustments for Monday
352
-
"09:00:00": 1, # Adjust standy agent count to 1
352
+
"09:00:00": 1, # Adjust standby agent count to 1
353
353
"17:00:00": 0# Adjust standby agent count to 0
354
354
},
355
355
{ # Schedule of standby agent count adjustments for Tuesday
@@ -505,7 +505,7 @@ A single `daysData` item contains a dictionary of times and standby agent counts
505
505
"daysData": [
506
506
{}, # Schedule of standby agent count adjustments for Sunday
507
507
{ # Schedule of standby agent count adjustments for Monday
508
-
"09:00:00": 1, # Adjust standy agent count to 1
508
+
"09:00:00": 1, # Adjust standby agent count to 1
509
509
"17:00:00": 0# Adjust standby agent count to 0
510
510
},
511
511
{ # Schedule of standby agent count adjustments for Tuesday
Copy file name to clipboardexpand all lines: docs/organizations/security/includes/environment-roles.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@
6
6
> |**Creator**| Global role, available from environments hub security option. Members of this role can create the environment in the project. Contributors are added as members by default. Required to trigger a YAML pipeline when the environment does not already exist.|
7
7
> |**Reader**| Members of this role can view the environment. |
8
8
> |**User**| Members of this role can use the environment when creating or editing YAML pipelines. |
9
-
> |**Administrator**| Members of this role can administer permissions, create, manage, view and use environments. For a particular environment, its creator is added as Admininistrator by default. Administrators can also open access to an environment to all pipelines. |
9
+
> |**Administrator**| Members of this role can administer permissions, create, manage, view and use environments. For a particular environment, its creator is added as Administrator by default. Administrators can also open access to an environment to all pipelines. |
> 
147
147
148
148
4. Enter the sign-in addresses or display name for each account you want to add. Add them one at a time or all at the same time. You can enter several identities into the text box, separated by commas.
Copy file name to clipboardexpand all lines: docs/organizations/settings/work/customize-process-work-item-type.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -94,7 +94,7 @@ To re-enable the WIT, choose **Enable** from the WIT context menu.
94
94
> [!NOTE]
95
95
> Disabling a WIT removes the WIT from the **New** drop down and add experiences. Creating a work item of that WIT is also blocked via REST APIs.
96
96
>
97
-
> No changes are made to existing work items of that type. You can update or delete them and they continue to appear on backlogs and boards. Both work item types need to be ebabled in order to do a change type operation.
97
+
> No changes are made to existing work items of that type. You can update or delete them and they continue to appear on backlogs and boards. Both work item types need to be enabled in order to do a change type operation.
Copy file name to clipboardexpand all lines: docs/organizations/settings/work/import-process/differences.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ Azure DevOps Services uses a different model than Team Foundation Server (TFS) f
29
29
The structure and overall syntax used in defining process templates remains the same, with only a few minor differences existing between templates you customize for import into Azure DevOps Services and those you upload to support an on-premises TFS.
30
30
31
31
> [!NOTE]
32
-
> Migration of projects or collections from Hosted XML to the inherited model is not support for Azure DevOps Server. It is only available on the Azure DevOps Sevice.
32
+
> Migration of projects or collections from Hosted XML to the inherited model is not support for Azure DevOps Server. It is only available on the Azure DevOps Services.
33
33
34
34
## Unsupported customizations and unreferenced plug-in files
35
35
@@ -81,4 +81,4 @@ When you connect to Azure DevOps Services, you can use the following tools subje
0 commit comments