Element
Description and syntax
Element | Description and syntax |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Element | Description |
|---|
Element | Description | |||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
GLOBALIST | Defines a set of LISTITEM elements that is stored for a project collection and that all projects in a collection can use. |
+
> [!NOTE]
>Depending on the process chosen when the project was created—[Agile](../work-items/guidance/agile-process.md), [Scrum](../work-items/guidance/scrum-process.md),
diff --git a/docs/boards/backlogs/backlogs-overview.md b/docs/boards/backlogs/backlogs-overview.md
index 466777e52dd..1346690238a 100644
--- a/docs/boards/backlogs/backlogs-overview.md
+++ b/docs/boards/backlogs/backlogs-overview.md
@@ -223,7 +223,7 @@ Items that are owned by other teams appear with an information icon, :::image t
Backlog displays with work item icons is supported for TFS 2017.2 and later versions. For TFS 2017.1 and earlier versions, items that are owned by other teams appear with hollow-filled bars.
-
+
::: moniker-end
::: moniker range="<= tfs-2015"
@@ -269,7 +269,7 @@ belong to one of three different teams: Customer Service, Phone, and Web.
::: moniker range="<= tfs-2015"
-
+
::: moniker-end
diff --git a/docs/boards/backlogs/connect-work-items-to-git-dev-ops.md b/docs/boards/backlogs/connect-work-items-to-git-dev-ops.md
index bd7138ef8c6..b52cd98321f 100644
--- a/docs/boards/backlogs/connect-work-items-to-git-dev-ops.md
+++ b/docs/boards/backlogs/connect-work-items-to-git-dev-ops.md
@@ -39,7 +39,7 @@ Review this article to learn:
The **Development** section records all Git development processes that support completion of the work item. This section can show your team information needed to take the next development step and minimize navigational steps to accomplish common development tasks. It also supports traceability, providing visibility into all the branches, commits, pull requests, and builds related to the work item.
+
::: moniker range="tfs-2017"
@@ -78,15 +78,15 @@ Consider creating a new branch when there are no linked code artifacts. If there
1. Start work on the work item by creating a branch. You can add a new Git branch from within the Development section...
- 
+
... or, from the form's :::image type="icon" source="../media/icons/actions-icon.png" border="false"::: Actions menu.
- 
+
Name the branch and select the repository on which it's based.
- 
+
Branches you create are automatically linked to the work item.
@@ -111,7 +111,7 @@ Consider creating a new branch when there are no linked code artifacts. If there
You create a pull request to merge the changes you made to a main branch and get your changes reviewed by other members of your team.
- 
+
5. Your view will switch to **Code**, Pull Requests page. Complete creating the pull request as shown.
@@ -144,11 +144,11 @@ You can also add a new branch from the work item listed on the backlog or Kanban
For example, here we select the first five items to link to a new branch.
-
+
And, we specify the name of the branch.
-
+
@@ -211,7 +211,7 @@ Keep in mind that the **Development** section only appears within the web portal
With Git commits, any work items that have been linked to a commit are listed under the Associated work items in the build summary page.
-
+
@@ -228,13 +228,13 @@ Hovering over any entry listed under the Development section activates the hyper
::: moniker range=">= azure-devops-2019"
The link types you can add within the development section are Branch, Build, Changeset, Commit, Found in build, Integrated in build, Pull Request, and Versioned Item.
-
+
::: moniker-end
::: moniker range=">= tfs-2017 <= tfs-2018"
The link types you can add within the development section are Branch, Build, Changeset, Commit, Pull Request, and Versioned Item.
-
+
::: moniker-end
diff --git a/docs/boards/backlogs/manage-issues-impediments.md b/docs/boards/backlogs/manage-issues-impediments.md
index 2fa1e10a189..aed06fe1f2d 100644
--- a/docs/boards/backlogs/manage-issues-impediments.md
+++ b/docs/boards/backlogs/manage-issues-impediments.md
@@ -99,7 +99,7 @@ Choose the :::image type="icon" source="../media/icons/pin-icon.png" border="fa
From **Work**, choose **Impediment** from the **New Work Item** list of options. Choose the :::image type="icon" source="../media/icons/pin-icon.png" border="false"::: pin icon to have it show up within **Work** drop down menu.
-
+
::: moniker-end
@@ -107,7 +107,7 @@ From **Work**, choose **Impediment** from the **New Work Item** list of options.
From the Queries page, choose Impediment from the **New** drop down menu.
-
+
::: moniker-end
diff --git a/docs/boards/backlogs/office/storyboard-your-ideas-using-powerpoint.md b/docs/boards/backlogs/office/storyboard-your-ideas-using-powerpoint.md
index 7be22c23901..713be2b3fcb 100644
--- a/docs/boards/backlogs/office/storyboard-your-ideas-using-powerpoint.md
+++ b/docs/boards/backlogs/office/storyboard-your-ideas-using-powerpoint.md
@@ -30,22 +30,22 @@ With storyboarding, you turn your ideas and goals into something visual. Your id
3. Open PowerPoint Storyboarding and start with a blank slide. You should see the **Storyboarding** ribbon and **Storyboard Shapes** library. If you don't see the Storyboarding ribbon, see step 2.
- 
+
Or, you can open PowerPoint Storyboarding from the work item **Storyboarding** tab.
- 
+
Or, from the web portal and the new work item form, choose the **Start storyboarding** menu option from any valid work item.
- 
+
> [!NOTE]
> Becuase this feature has been deprecated, the **Start storyboarding** menu option is no longer available from the web form for Azure DevOps Services or Azure DevOps Server 2019 and later versions.
4. Add a background shape that's appropriate for your app. To add a shape, just drag it onto the slide.
- 
+
5. Search for more shapes to complete your design.
@@ -98,7 +98,7 @@ When you share your storyboards to a shared network location, you can link the s
7. And, whoever views the work item can also access the storyboard.
- 
+
With PowerPoint Storyboarding, you can illustrate a new or a modified interface. You can capture existing user interfaces and build a storyboard from a collection of predefined storyboard shapes. Also, you can customize the slide layouts for your web, client, or phone applications. And, by linking the storyboard to the product backlog item or user story, you automatically share it with your team.
diff --git a/docs/boards/boards/add-columns.md b/docs/boards/boards/add-columns.md
index a25a8f287a3..0c7e35ce0f7 100644
--- a/docs/boards/boards/add-columns.md
+++ b/docs/boards/boards/add-columns.md
@@ -125,7 +125,7 @@ Choose **Correct this now** to open the **Settings** dialog.
In this example two new states have been added, **Triaged** for bug, and **Investigate** for user story. Each state needs to be mapped to an existing or new column in order for the Kanban board to display work items assigned to these states.
-
+
::: moniker-end
::: moniker range="tfs-2015"
@@ -133,7 +133,7 @@ In this example two new states have been added, **Triaged** for bug, and **Inves
**TFS 2015.1**
In this example two new states have been added, **Triaged** for bug, and **Investigate** for user story. Each state needs to be mapped to an existing or new column in order for the Kanban board to display work items assigned to these states.
-
+
**TFS 2015**
In this example, bugs have been added to show on the Kanban board. You need to map the bug state for each column on the Kanban board.
@@ -253,7 +253,7 @@ You'll see different column titles and choices based on the [Process](../work-it
Or, you can open the dialog and change one or more settings for a Kanban column.
- 
+
4. To change the column order, drag the column tab to the position you want.
@@ -292,7 +292,7 @@ You'll see different column titles and choices based on the [Process](../work-it
Or, you can open the dialog and change one or more settings for a Kanban column.
-
+
4. To change the column order, drag the column tab to the position you want.
diff --git a/docs/boards/boards/add-run-update-tests.md b/docs/boards/boards/add-run-update-tests.md
index 6a5b276cfc4..71deabc4c83 100644
--- a/docs/boards/boards/add-run-update-tests.md
+++ b/docs/boards/boards/add-run-update-tests.md
@@ -25,7 +25,7 @@ In this article, you'll learn:
> * How to expand or collapse inline tests
> * How to reorder or reparent inline tests
-
+
Tests you create from the Kanban board are automatically linked to the user story or backlog item.
@@ -87,11 +87,11 @@ Tests you create from the Kanban board are automatically linked to the user stor
2. If you have a number of tests to add, simply keep typing each title and click Enter.
- 
+
To add details to the test case, open it. You can click the title, double-click the inline item, or open the context menu and choose Open.
- 
+
See [Create manual tests](../../test/create-test-cases.md) to learn more about defining tests.
@@ -101,7 +101,7 @@ Prior to running the test, you must add details.
Run the test by selecting  Run test from the :::image type="icon" source="../media/icons/actions-icon.png" border="false"::: actions menu for the inline test.
-
+
Microsoft Test Runner starts in a new browser instance. For details on running a test, see [Run manual tests](../../test/run-manual-tests.md).
@@ -110,7 +110,7 @@ Microsoft Test Runner starts in a new browser instance. For details on running a
You can update the status of the test from the :::image type="icon" source="../media/icons/actions-icon.png" border="false"::: actions menu .
-
+
Updating the status of tests enable you to track test results.
diff --git a/docs/boards/boards/add-task-checklists.md b/docs/boards/boards/add-task-checklists.md
index 1795d223c84..29e0c574333 100644
--- a/docs/boards/boards/add-task-checklists.md
+++ b/docs/boards/boards/add-task-checklists.md
@@ -25,7 +25,7 @@ With checklists or to do lists, you continue to enjoy lightweight tracking. You
:::image type="content" source="media/checklists/board-checklists.png" alt-text="Screenshot of product-level Kanban board with three work items showing child lists":::
::: moniker-end
::: moniker range="<= tfs-2018"
-
+
::: moniker-end
In this article, you'll learn:
@@ -75,10 +75,10 @@ In this example, tasks are added to the product Kanban board using the checklist
:::image type="content" source="media/checklists/add-task-menu.png" alt-text="Screenshot of open the context menu of work item to add a task.":::
::: moniker-end
::: moniker range=">= tfs-2017 <= tfs-2018"
- 
+
::: moniker-end
::: moniker range="tfs-2015"
- 
+
::: moniker-end
2. If you have many tasks to add, keep typing their titles and choose Enter after each title.
@@ -86,7 +86,7 @@ In this example, tasks are added to the product Kanban board using the checklist
:::image type="content" source="media/checklists/four-tasks-added.png" alt-text="Screenshot of added tasks.":::
::: moniker-end
::: moniker range="<= tfs-2018"
- 
+
::: moniker-end
::: moniker range=">= tfs-2017"
3. If you have details you want to add about a task, open the item by choosing the title.
@@ -95,11 +95,11 @@ In this example, tasks are added to the product Kanban board using the checklist
::: moniker range="tfs-2015"
4. If you have details you want to add about a task, open the parent work item and then choose the :::image type="icon" source="../media/icons/icon-links-tab-wi.png" border="false"::: links icon/tab.
- 
+
Double-click the task, or select and press the Enter key, to open it.
- 
+
::: moniker-end
> [!NOTE]
@@ -114,7 +114,7 @@ When you complete a task or other checklist item, simply choose the checkbox to
:::image type="content" source="media/checklists/board-checklists.png" alt-text="Screenshot of product-level Kanban board showing several done child items":::
::: moniker-end
::: moniker range="<= tfs-2018"
-
+
::: moniker-end
The State of the work item is updated from **Active** to **Closed** for Agile and CMMI projects and from **To Do** to **Done** for Scrum projects, and
@@ -130,7 +130,7 @@ Upon first opening the Kanban board, you'll see an unexpanded view of checklists
:::image type="content" source="media/checklists/unexpanded-checklists.png" alt-text="Screenshot of unexpanded checklist":::
::: moniker-end
::: moniker range="<= tfs-2018"
-
+
::: moniker-end
diff --git a/docs/boards/boards/best-practices-kanban.md b/docs/boards/boards/best-practices-kanban.md
index 4a74d59eb60..4a577157672 100644
--- a/docs/boards/boards/best-practices-kanban.md
+++ b/docs/boards/boards/best-practices-kanban.md
@@ -143,7 +143,7 @@ Acceptance criteria corresponds to what a customer should expect when a user sto
Acceptance criteria defines when a feature is shippable. Capture the criteria for each backlog item in the Acceptance Criteria field (for Scrum product backlog items) or the Description field (for Agile user stories and CMMI requirements).
-![Acceptance criteria field on work item form]](media/vso-product-backlog-work-item-form-acceptance-criteria.png)
+
The Definition of Done, on the other hand, is about delivering an incremental piece of a feature as it moves from not started to complete. Agile teams meet with greater success when each handoff made is in a ready state for the recipient to begin their work.
diff --git a/docs/boards/boards/customize-cards.md b/docs/boards/boards/customize-cards.md
index c71d053cac2..fee1fd93839 100644
--- a/docs/boards/boards/customize-cards.md
+++ b/docs/boards/boards/customize-cards.md
@@ -546,7 +546,7 @@ You can control the test plan under which inline tests you add through the Kanba
From a card on the Kanban board, you can easily navigate to the underlying test plan and test suite under which the tests are created. Choose the :::image type="icon" source="../../media/icons/open-icon.png" border="false"::: open icon to open another browser tab showing **Test** and associated test plan and test suite that controls the inline tests.
-
+
::: moniker-end
diff --git a/docs/boards/boards/definition-of-done.md b/docs/boards/boards/definition-of-done.md
index 6f45b0a5171..4668b27d3a1 100644
--- a/docs/boards/boards/definition-of-done.md
+++ b/docs/boards/boards/definition-of-done.md
@@ -89,7 +89,7 @@ If you're just getting started, review [Kanban basics](kanban-basics.md) to get
7. Choose **Columns** and then a column tab to configure the Definition of Done for that column. You can specify the Definition of Done for each intermediate column on your team's Kanban board.
- ![Kanban board, Coding column tab, Definition of done]](media/vso-kanban-board-definition-of-done-no-tags.png)
+
For TFS 2015
8. Choose **Edit Definition** within an intermediate column tab and specify the Definition of Done for that column.
diff --git a/docs/boards/boards/expedite-work.md b/docs/boards/boards/expedite-work.md
index 9eac031ec4d..7222e7607a8 100644
--- a/docs/boards/boards/expedite-work.md
+++ b/docs/boards/boards/expedite-work.md
@@ -152,7 +152,7 @@ Once you've identified one or two, add them to your Kanban board.
9. Choose **Swimlanes**, and then choose the :::image type="icon" source="../media/icons/add_icon.png" border="false"::: plus icon, and enter the name of the swimlane you want to add.
**For TFS 2015.1 and later versions**
- 
+
The default lane appears unlabeled on the Kanban board. You can rename it to anything you like, however, you can't delete it. Also, you can rename it directly from the Kanban board.
**For TFS 2015**
@@ -190,7 +190,7 @@ You can track Kanban board swimlane moves by creating a query and using the [Boa
Similar to the way [column moves are tracked](add-columns.md), swimlane moves are captured in the history field.
-
+
For TFS 2015 and earlier versions, you can't [query](../queries/using-queries.md) for all items in a particular swimlane. To perform such a query, you'd have to assign a value to a field, such as the Priority field, or [tag](../queries/add-tags-to-work-items.md) each item in a similar way.
::: moniker-end
diff --git a/docs/boards/boards/kanban-basics.md b/docs/boards/boards/kanban-basics.md
index 1528366dc55..8108d35e394 100644
--- a/docs/boards/boards/kanban-basics.md
+++ b/docs/boards/boards/kanban-basics.md
@@ -97,7 +97,7 @@ Once you've configured your Kanban board to match how your team works, you&#
Here are a few things you can do. See at a glance the estimated size of work for each item which displays at the bottom right of each card. Add items to your backlog in the first column. When priorities change, move items up and down within a column. And, as work completes in one stage, update the status of an item by moving it to a downstream stage.
-
+
::: moniker range="tfs-2015"
@@ -110,7 +110,7 @@ Here are a few things you can do. See at a glance the estimated size of work for
Also, you can quickly update a field or reassign ownership directly from the board.
-
+
::: moniker-end
@@ -148,11 +148,11 @@ The selections you make are only set for you, and persist across sessions until
Choose the chart as shown in the following image.
-
+
The CFD shows the count of items in each Kanban column for the past 30 weeks or less. From this chart you can gain an idea of the amount of work in progress and lead time. Work in progress counts unfinished requirements. Lead time indicates the amount of time it takes to complete a requirement from the time it was first proposed.
-
+
::: moniker-end
diff --git a/docs/boards/boards/kanban-board-controls.md b/docs/boards/boards/kanban-board-controls.md
index 54ae128f17b..d03d5f20d71 100644
--- a/docs/boards/boards/kanban-board-controls.md
+++ b/docs/boards/boards/kanban-board-controls.md
@@ -66,7 +66,7 @@ You can quickly switch from the backlog view to the board view using the **Backl
Enter **?** to open the Kanban board keyboard shortcuts.
-
+
::: moniker-end
diff --git a/docs/boards/boards/kanban-overview.md b/docs/boards/boards/kanban-overview.md
index ca01c88efa3..17d62555fb8 100644
--- a/docs/boards/boards/kanban-overview.md
+++ b/docs/boards/boards/kanban-overview.md
@@ -143,7 +143,7 @@ The Average work in progress value excludes completed work items. Use the intera
::: moniker range="<= azure-devops-2019"
-
+
The CFD shows the count of items in each Kanban column for the past 30 weeks or less. From this chart you can gain an idea of the amount of work in progress and lead time. Work in progress counts unfinished requirements. Lead time indicates the amount of time it takes to complete a requirement from the time it was first proposed.
diff --git a/docs/boards/boards/wip-limits.md b/docs/boards/boards/wip-limits.md
index 82284382b43..8a587621a4a 100644
--- a/docs/boards/boards/wip-limits.md
+++ b/docs/boards/boards/wip-limits.md
@@ -21,7 +21,7 @@ An essential Kanban practice—Work in Progress limits, referred to as "WIP
You define WIP limits for each work stage, corresponding to each intermediate column. The limit sets a soft constraint on the number of items allowed within the column. Nothing actually prevents you from moving more items into the column and exceeding the limit. Your Kanban board shows the count of items at each stage next to each limit.
-
+
While [setting WIP limits](#Set) is simple, adhering to the limits takes a team commitment. Successful adoption of WIP limits involves a culture change. It moves teams from a focus on individual productivity to one of team productivity.
@@ -52,7 +52,7 @@ After you've set your WIP limits, you'll want to track how well your team keeps
Respecting WIP limits means teams don't pull items into a column if doing so causes the number of items in the column to exceed the column limit. When they do, your Kanban board provides immediate feedback. This feedback should act as a signal to the team to focus immediately on activities to reduce the number of items in the column.
-
+
Although simple in theory, keeping within WIP limits can force individuals, teams, and organizations out of their comfort zone. Team members who like to multitask might feel unnecessarily constrained. Others might find themselves without work as they wait for work to complete at an upstream stage.
diff --git a/docs/boards/plans/configure-hierarchical-teams.md b/docs/boards/plans/configure-hierarchical-teams.md
index b89396e53c1..238b1b920ca 100644
--- a/docs/boards/plans/configure-hierarchical-teams.md
+++ b/docs/boards/plans/configure-hierarchical-teams.md
@@ -175,7 +175,7 @@ You do this by opening each area path associated with a feature team and changin
For example, here we move the Customer Profile to under Account Management.
- 
+
Repeat this step for all feature team area paths.
@@ -249,7 +249,7 @@ From **Areas**, open the :::image type="icon" source="../media/icons/context_men
Here we choose to include sub-area paths for the Account Management area.
-
+
Repeat this step for all your management areas. Also, if you want to enable rollup across all feature teams and management areas to the top level area, repeat this step for the default team. In our example, that corresponds to Fabrikam.
diff --git a/docs/boards/plans/portfolio-management.md b/docs/boards/plans/portfolio-management.md
index 85d81b5ff1c..a00f6a794c5 100644
--- a/docs/boards/plans/portfolio-management.md
+++ b/docs/boards/plans/portfolio-management.md
@@ -66,7 +66,7 @@ The Fabrikam Account Management portfolio owner has several campaigns to initiat
With the hierarchical structure implemented, portfolio owners working in Account Management can view the epic, feature, and product backlogs for their area.
-
+
All work items under the Fabrikam/Account Management area path appear in their backlog view. You can expand a single item or use the expand  and collapse  icons to expand or collapse one level of the hierarchy.
@@ -115,7 +115,7 @@ Items that are owned by other teams appear with an information icon, :::image t
Backlog displays with work item icons is supported for TFS 2017.2 and later versions. For TFS 2017.1 and earlier versions, items that are owned by other teams appear with hollow-filled bars.
-
+
::: moniker-end
@@ -123,7 +123,7 @@ Backlog displays with work item icons is supported for TFS 2017.2 and later vers
The Customer Profile feature team's view of the backlog only includes those work items assigned to their area path, **Fabrikam/Account Management/Customer Profile**. Here we show parents which provides a few of the features and epics to which the backlog items belong. Items that are owned by other teams appear with hollow-filled bars. For example, Mobile feedback and Text alerts belong to the Account Management team.
-
+
::: moniker-end
@@ -175,7 +175,7 @@ Here, all backlog items have been assigned to feature teams. While all features
In this view of the Account Management backlog, all items still assigned to **Account Management** have yet to be assigned.
-
+
During the planning meeting, you can open each item, make notes, and assign the item to the team to work on it.
diff --git a/docs/boards/plans/visibility-across-teams.md b/docs/boards/plans/visibility-across-teams.md
index bb7134de2cc..c0ce628565b 100644
--- a/docs/boards/plans/visibility-across-teams.md
+++ b/docs/boards/plans/visibility-across-teams.md
@@ -155,7 +155,7 @@ The two areas of most interest to management teams are project health and bug de
For example, here we've added three query-based charts, one for each team, to a dashboard that shows the active and resolved bugs over the previous 4 weeks.
-
+
When defining multi-team dashboards, consider the following:
diff --git a/docs/boards/queries/history-and-auditing.md b/docs/boards/queries/history-and-auditing.md
index 7c9a583c6c1..f6964dcdf41 100644
--- a/docs/boards/queries/history-and-auditing.md
+++ b/docs/boards/queries/history-and-auditing.md
@@ -36,11 +36,11 @@ You can use either the web portal or Team Explorer to view the history of a work
::: moniker range=">= tfs-2017"
-
+
::: moniker-end
::: moniker range=">= tfs-2013 <= tfs-2015"
-
+
::: moniker-end
diff --git a/docs/boards/queries/query-by-workflow-changes.md b/docs/boards/queries/query-by-workflow-changes.md
index 287a6539f59..6bbeac09220 100644
--- a/docs/boards/queries/query-by-workflow-changes.md
+++ b/docs/boards/queries/query-by-workflow-changes.md
@@ -319,7 +319,7 @@ Using the Kanban query fields—Board Column, Board Column Done, and Board L
For example, you can list items based on the team area path, and if they are in a specific custom Kanban column and swimlane. If you rename a column or swimlane, you'll need to update the query filters to reflect the new name. For more ideas, see this blog post: [New fields bring Kanban goodness to queries, and more](https://blogs.msdn.microsoft.com/devops/2015/10/19/new-fields-bring-kanban-goodness-to-queries-and-more/)
-
+
> [!NOTE]
> Queries are now scoped to the current project by default. Check the **Query across projects** to find work items defined in other projects within the collection.
diff --git a/docs/boards/queries/query-numeric.md b/docs/boards/queries/query-numeric.md
index 75a501e7a69..e1a720f2c60 100644
--- a/docs/boards/queries/query-numeric.md
+++ b/docs/boards/queries/query-numeric.md
@@ -102,7 +102,7 @@ Create an active bugs query and modify the column options to show Assigned To a
::: moniker-end
::: moniker range="<= tfs-2018"
-
+
::: moniker-end
### Count of bugs by state and area
@@ -196,7 +196,7 @@ Based on the process your project references, you can assign the following field
If you follow Scrum practices and estimate Remaining Work for your tasks and bugs, you can get a roll up of the amount of work remaining for each developer with the following query and chart. By using the In operator and including both Task and Bug, you include any bugs that are being tracked as tasks.
-
+
Add Remaining Work as a column option to the query and save. To view a sum of the remaining work, add a pivot chart as shown.
@@ -206,7 +206,7 @@ Add Remaining Work as a column option to the query and save. To view a sum of th
::: moniker-end
::: moniker range="<= tfs-2018"
-
+
::: moniker-end
::: moniker range="tfs-2013"
diff --git a/docs/boards/queries/set-query-permissions.md b/docs/boards/queries/set-query-permissions.md
index 84ca2891c39..b7e064b9bf2 100644
--- a/docs/boards/queries/set-query-permissions.md
+++ b/docs/boards/queries/set-query-permissions.md
@@ -136,7 +136,7 @@ If you're not a member of the project administrators group, [get added](../../or
Here we add the Web team and grant them permissions to create and manage permissions to all queries and folders under the Triage folder.
- 
+
Choose the **Add...** menu to add a user identity or group.
diff --git a/docs/boards/queries/share-plans.md b/docs/boards/queries/share-plans.md
index e771363f643..4966ca8920b 100644
--- a/docs/boards/queries/share-plans.md
+++ b/docs/boards/queries/share-plans.md
@@ -242,7 +242,7 @@ You can edit, open, save, or delete an attachment by choosing an attachment and
Choose the **Attachments** tab icon to attach a file to the work item.
-
+
Choose the  plus icon to add an attachment. Choose an item and then choose :::image type="icon" source="../media/icons/open-icon.png" border="false"::: the open icon to open the attachment or :::image type="icon" source="../media/icons/download-icon.png" border="false"::: download icon to save a copy.
@@ -290,7 +290,7 @@ To open PowerPoint with storyboarding, see [Storyboard your ideas using PowerPoi
::: moniker range=">= tfs-2017"
You can open Storyboarding with PowerPoint from the :::image type="icon" source="../media/icons/actions-icon.png" border="false"::: actions menu within a work item form.
-
+
To link to an existing storyboard, click the  Links tab and add a storyboard link.
::: moniker-end
diff --git a/docs/boards/queries/triage-work-items.md b/docs/boards/queries/triage-work-items.md
index 69b973fe08b..528840662c7 100644
--- a/docs/boards/queries/triage-work-items.md
+++ b/docs/boards/queries/triage-work-items.md
@@ -128,7 +128,7 @@ Work items shown in bold text indicate that local changes have not yet been save
::: moniker range=">= azure-devops-2019"
Choose **Save items** to save all work items you've modified.
-
+
::: moniker-end
diff --git a/docs/boards/queries/using-queries.md b/docs/boards/queries/using-queries.md
index eafb47687c8..4cf119c5de4 100644
--- a/docs/boards/queries/using-queries.md
+++ b/docs/boards/queries/using-queries.md
@@ -257,7 +257,7 @@ By default, new queries are scoped to the current project. However, you can crea
To list work items defined in two or more projects, checkmark **Query across projects**. For example, the following query finds all features created in all projects within the last 30 days.
-
+
::: moniker-end
diff --git a/docs/boards/sprints/customize-taskboard.md b/docs/boards/sprints/customize-taskboard.md
index 45cc12d137c..1487d65e1c0 100644
--- a/docs/boards/sprints/customize-taskboard.md
+++ b/docs/boards/sprints/customize-taskboard.md
@@ -285,9 +285,9 @@ You change the way cards appear on the Taskboard in the same way you change the
3. Place a check mark in the check box for those fields you want to have appear on the board.
**TFS 2015.1 options:**
- 
+
**TFS 2015 options:**
- 
+
Repeat this step for each work item type you want to change. Don't be surprised if the options change when you choose a different work item type. For example, **Show Remaining Work** only applies to tasks and perhaps bugs, but not to user stories or product backlog items.
diff --git a/docs/boards/sprints/define-sprints.md b/docs/boards/sprints/define-sprints.md
index ee6c3f833b3..cb06ec2a303 100644
--- a/docs/boards/sprints/define-sprints.md
+++ b/docs/boards/sprints/define-sprints.md
@@ -113,7 +113,7 @@ To quickly get started, you can use the default sprints, also referred to as ite
2. Choose the sprint listed under **Current** and then choose **Set dates**.
- 
+
> [!NOTE]
> If you don't see any sprints listed or the **Set dates** link, then no sprints have been selected for the team context you've selected. To select sprints for the team context, see [Define iteration (sprint) paths and configure team iterations](../../organizations/settings/set-iteration-paths-sprints.md). To switch team context, see [Switch project or team focus](../../project/navigation/go-to-project-repo.md).
diff --git a/docs/boards/sprints/task-board.md b/docs/boards/sprints/task-board.md
index 6dd87ab7bf5..dcce5bdc3c4 100644
--- a/docs/boards/sprints/task-board.md
+++ b/docs/boards/sprints/task-board.md
@@ -397,7 +397,7 @@ Requires TFS 2015.1 or later version.
- From the taskboard, drag the PBI or user story from the first column onto the backlog or future sprint. All child tasks automatically move with the parent item.
- From the sprint backlog, multi-select the items to move and then click the context menu for an item and select the iteration to move them to.
- 
+
::: moniker-end
::: moniker range="tfs-2013"
@@ -405,7 +405,7 @@ Requires TFS 2015.1 or later version.
- From the sprint backlog, drag an item back to the backlog or to another sprint.
- 
+
- If you need to move several items, you can create a query from the sprint backlog and then use the query to [bulk modify the iteration path](../backlogs/bulk-modify-work-items.md).
::: moniker-end
diff --git a/docs/boards/work-items/email-work-items.md b/docs/boards/work-items/email-work-items.md
index 682349cdba5..bb9e4458790 100644
--- a/docs/boards/work-items/email-work-items.md
+++ b/docs/boards/work-items/email-work-items.md
@@ -326,7 +326,7 @@ Some teams want to work with physical cards when planning or updating their phys
**From the web portal**, simply copy the URL from the web browser address or hover over the title and then click the  copy-to-clipboard icon.
-
+
::: moniker-end
diff --git a/docs/boards/work-items/follow-work-items.md b/docs/boards/work-items/follow-work-items.md
index c89e6abbe0c..6434e40e1ac 100644
--- a/docs/boards/work-items/follow-work-items.md
+++ b/docs/boards/work-items/follow-work-items.md
@@ -105,7 +105,7 @@ To stop following changes, choose the :::image type="icon" source="../media/ico
To track the progress of a single pull request, choose the :::image type="icon" source="../media/icons/actions-icon.png" border="false"::: actions icon for the pull request, and select the :::image type="icon" source="../media/icons/follow-icon.png" border="false"::: **Follow** option. This signals the system to notify you when changes are made to the PR.
-
+
You'll only receive notifications when other members of your team modifies the PR, such as adding to the discussion or adding an attachment.
@@ -144,7 +144,7 @@ You can also view and manage work that you're following from **Boards>Work Items
Open **Work>Queries** and choose **Followed work items**.
-
+
From this view, you can view all items you're following across all projects. Also, you can perform similar actions supported with a query results view, such as:
- Refresh the view
diff --git a/docs/boards/work-items/guidance/agile-process-workflow.md b/docs/boards/work-items/guidance/agile-process-workflow.md
index 636cc4ecf68..5f0ddf85c38 100644
--- a/docs/boards/work-items/guidance/agile-process-workflow.md
+++ b/docs/boards/work-items/guidance/agile-process-workflow.md
@@ -97,7 +97,7 @@ Use the following guidance and that provided for [fields used in common across w
As work progresses, you change the State field to update the status. Optionally, you can specify a reason. The state and reason fields appear on the work item form in the header area.
-
+
### Agile workflow states
@@ -141,7 +141,7 @@ When your team manages their work in sprints, they can use the [sprint backlog p
Name the task and estimate the work it will take.
-
+
Using Agile processes, teams forecast work and define tasks at the start of each sprint, and each team member performs a subset of those tasks. Tasks can include development, testing, and other kinds of work. For example, a developer can define tasks to implement user stories, and a tester can define tasks to write and run test cases.
@@ -186,7 +186,7 @@ From the web portal or Test Manager, you can [create test cases that automatical
The test case contains a number of fields, many of which are automated and integrated with Test Manager and the build process. For a description of each field, see [Query based on build and test integration fields](../../queries/build-test-integration.md).
-
+
The :::image type="icon" source="../../backlogs/media/icon-links-tab-wi.png" border="false"::: (links tab) captures the links to user stories and bugs in a test case. By linking user stories and bugs to test cases, the team can track the progress made in testing each item. By defining these links, you support information that appears in the [Stories Overview Report](../../../report/sql-reports/stories-overview-report-agile.md) report.
diff --git a/docs/boards/work-items/guidance/cmmi-process-workflow.md b/docs/boards/work-items/guidance/cmmi-process-workflow.md
index 4f18adf302c..b2a701533f3 100644
--- a/docs/boards/work-items/guidance/cmmi-process-workflow.md
+++ b/docs/boards/work-items/guidance/cmmi-process-workflow.md
@@ -296,7 +296,7 @@ Use the following guidance and that provided for [fields used in common across w
As work progresses, you change the State field to update the status. Optionally, you can specify a reason. The state and reason fields appear on the work item form in the header area.
-
+
### CMMI workflow states
diff --git a/docs/boards/work-items/guidance/cmmi-process.md b/docs/boards/work-items/guidance/cmmi-process.md
index ae52b59d070..4f43d6532ca 100644
--- a/docs/boards/work-items/guidance/cmmi-process.md
+++ b/docs/boards/work-items/guidance/cmmi-process.md
@@ -20,7 +20,7 @@ ms.date: 04/11/2019
The CMMI process supports the following work item types (WITs) to plan and track work, tests, feedback, and code review. With different WITs you can track different types of work—such as requirements, change requests, tasks, bugs and more. These artifacts are created when you create a project using the CMMI process. They are based on the [Capability Maturity Model Integration (CMMI)](./cmmi/guidance-background-to-cmmi.md?viewFallbackFrom=vsts) process.
-
+
In addition to the WITs, teams have access to a set of work item queries to track information, analyze progress, and make decisions.
diff --git a/docs/boards/work-items/guidance/scrum-process-workflow.md b/docs/boards/work-items/guidance/scrum-process-workflow.md
index 1b2bb453bc0..94c7d1ec0be 100644
--- a/docs/boards/work-items/guidance/scrum-process-workflow.md
+++ b/docs/boards/work-items/guidance/scrum-process-workflow.md
@@ -34,7 +34,7 @@ When you define a product backlog item, you want to focus on the value that your
You can create PBIs and bugs from the [quick add panel on the product backlog page](../../backlogs/create-your-backlog.md).
-
+
Later, you can open each PBI or bug to provide more details and estimate the effort. Also, by prioritizing the PBIs and bugs on the backlog page (which is captured in the Backlog Priority field), product owners can indicate which items should be given higher priority.
@@ -81,7 +81,7 @@ Use the following guidance and that provided for [fields used in common across w
As work progresses, you change the State field to update the status. Optionally, you can specify a reason. The state and reason fields appear on the work item form in the header area.
-
+
### Scrum workflow states
@@ -124,7 +124,7 @@ When your team manages their work in sprints, they can use the sprint backlog pa
Name the task and estimate the work it will take.
-
+
Using Scrum, teams forecast work and define tasks at the start of each sprint, and each team member performs a subset of those tasks. Tasks can include development, testing, and other kinds of work. For example, a developer can define tasks to implement PBIs, and a tester can define tasks to write and run test cases.
@@ -150,7 +150,7 @@ When teams estimate work using hours or days, they define tasks and the **Remain
From the web portal or Test Manager, you can [create test cases that automatically link to a PBI or bug](../../../test/create-test-cases.md). Or, you can link a PBI or bug to a test case from the :::image type="icon" source="../../backlogs/media/icon-links-tab-wi.png" border="false"::: (links tab).
-
+
The test case contains a number of fields, many of which are automated and integrated with Test Manager and the build process. For a description of each field, see [Query based on build and test integration fields](../../queries/build-test-integration.md).
diff --git a/docs/boards/work-items/work-item-form-controls.md b/docs/boards/work-items/work-item-form-controls.md
index 4196a7c6b7e..f6ba0b0aa56 100644
--- a/docs/boards/work-items/work-item-form-controls.md
+++ b/docs/boards/work-items/work-item-form-controls.md
@@ -75,7 +75,7 @@ As the following image shows, each work item form comes with a number of control
As work progresses, team members can update the state and reassign it as needed.
-
+
While the workflow states differ for different work item types, they usually follow a progression from New or Active to Closed or Done. The following image shows the work flow states for the Agile process user story. If you want to discard a work item, change the state to Removed.
@@ -110,7 +110,7 @@ Removed work items remain in the data store and can be reactivated by changing t
With each update, the Reason field also updates and changes are recorded in the History field which you can view through the  **History** tab. To find work items based on their history, see [History & auditing](../queries/history-and-auditing.md).
-
+
@@ -122,7 +122,7 @@ By linking work items using Related or Dependent link types, you can track work
There are three links controls provided on most forms. The Development and Related Work scoped links controls appear on the Details tab. The  Links tab provides access to all links made to the work item.
-
+
## Add links
@@ -133,7 +133,7 @@ From each links control, you can perform these actions:
- To delete a link, highlight it and click the  delete icon
- To link to an existing item, or create and link a new work item, select one of the menu options.
-
+
To learn more, see [Add links to work items](../backlogs/add-link.md).
@@ -155,7 +155,7 @@ The Related Work links control displays links to other work items in a set order
In addition, the Links control tab provides access to all links made to the work item—both work items and external objects.
-
+
diff --git a/docs/organizations/projects/project-vision-status.md b/docs/organizations/projects/project-vision-status.md
index d1bb568a649..ec820735ab0 100644
--- a/docs/organizations/projects/project-vision-status.md
+++ b/docs/organizations/projects/project-vision-status.md
@@ -274,7 +274,7 @@ You can change the repository used to support your project vision, including poi
2. From the select file dialog, choose an existing repo from the drop-down menu, or choose the Wiki option, shown as follows.
- 
+
> [!TIP]
> Only the Wiki home page displays. To access additional Wiki pages, go to the Wiki.
@@ -290,7 +290,7 @@ You can change the repository used to support your project vision, including poi
diff --git a/docs/organizations/settings/work/manage-process.md b/docs/organizations/settings/work/manage-process.md
index 040dd5ac7f8..1d0abd9f3c0 100644
--- a/docs/organizations/settings/work/manage-process.md
+++ b/docs/organizations/settings/work/manage-process.md
@@ -58,7 +58,7 @@ You can create an inherited process from any one of the four system processes:[B
1. Enter a name for your process and optionally a description. (For naming restrictions, see [About process customization and inherited processes, Process name restrictions](inheritance-process-model.md#process-naming).
- 
+
Once you've defined the inherited process, you can perform these actions:
- [Customize a project using an inherited process](customize-process.md)
diff --git a/docs/reference/add-modify-wit.md b/docs/reference/add-modify-wit.md
index c2dcf0193c3..27f86301991 100644
--- a/docs/reference/add-modify-wit.md
+++ b/docs/reference/add-modify-wit.md
@@ -203,7 +203,7 @@ In the web portal, work items appear in query results and on the backlog and boa
> [!NOTE]
>**Feature availability:** For On-premises XML, you can customize the workflow state color for TFS 2015.2 or later versions, and you can customize the WIT icon for TFS 2017.2 and later versions.
-
+
## Change the type of an existing work item
diff --git a/docs/reference/manage-new-form-rollout.md b/docs/reference/manage-new-form-rollout.md
index 1f65f10b94b..32f23a5deeb 100644
--- a/docs/reference/manage-new-form-rollout.md
+++ b/docs/reference/manage-new-form-rollout.md
@@ -34,7 +34,7 @@ You enable the new form from the project collection admin page.
1. To start, choose the :::image type="icon" source="../media/icons/gear_icon.png" border="false"::: gear Settings icon to open the admin context for the project collection.
- 
+
2. From the collection admin page, click **Enable the new work item form**.
diff --git a/docs/reference/process-templates/customize-process.md b/docs/reference/process-templates/customize-process.md
index 003136e0812..f03eea2c18b 100644
--- a/docs/reference/process-templates/customize-process.md
+++ b/docs/reference/process-templates/customize-process.md
@@ -106,31 +106,31 @@ To customize a process template, you customize one or more files associated with
#### Teams, groups, permissions, & area and iteration paths
+
For an overview of using the web portal, see [Web portal navigation](../../project/navigation/index.md?toc=/azure/devops/user-guide/toc.json&bc=/azure/devops/user-guide/breadcrumb/toc.json).
diff --git a/docs/reference/process/new-work-item-experience.md b/docs/reference/process/new-work-item-experience.md
index 544ed74618a..5bf9b06cd0f 100644
--- a/docs/reference/process/new-work-item-experience.md
+++ b/docs/reference/process/new-work-item-experience.md
@@ -56,7 +56,7 @@ Your data has more structure and organization. Plus, you can focus more easily o
All the core tabs—Details, History, Links, and Attachments—now have more screen space. See [History and auditing](../../boards/queries/history-and-auditing.md) for details on the new History tab.
-
+
### Discussion
@@ -67,7 +67,7 @@ Click the 
Within the discussion section, you can use the [@mention control](../../notifications/at-mentions.md) to notify another team member about the discussion. Simply type **@** and their name. To reference a work item, use the [**#ID** control](../../notifications/add-links-to-work-items.md). Type **#** and a list of work items that you've recently referenced will appear from which you can select.
-
+
> [!IMPORTANT]
> For on-premises TFS, [you must configure an SMTP server](/azure/devops/server/admin/setup-customize-alerts) in order for team members to receive notifications.
@@ -76,7 +76,7 @@ Within the discussion section, you can use the [@mention contro
Looking for the toolbar task options? You access them now through the :::image type="icon" source="../../media/icons/actions-icon.png" border="false"::: actions icon.
-
+
## Switch to the new experience
diff --git a/docs/reference/xml/all-field-xml-elements-reference.md b/docs/reference/xml/all-field-xml-elements-reference.md
index eabf2ce0000..c3033aedce2 100644
--- a/docs/reference/xml/all-field-xml-elements-reference.md
+++ b/docs/reference/xml/all-field-xml-elements-reference.md
@@ -62,8 +62,8 @@ Use child elements to set various restrictions on what data can be entered into
To learn how to use these elements, see [Rules and rule evaluation](../../organizations/settings/work/rule-reference.md). Restrictions exist on applying most rules to system fields. All child elements are optional.
-Element | Description and syntax |
+
|---|
Element | Description and syntax |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Element | Description |
|---|
Element | Description | |||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
GLOBALIST | Defines a set of LISTITEM elements that is stored for a project collection and that all projects in a collection can use. |
+
+
+
+
+
+
+
+ 
+ 
+ 
+
+
+ 
+