move bookmarks above monikers to address issues when archiving.

Author: KathrynEE

Diff for: docs/boards/backlogs/manage-bugs.md

@@ -396,14 +396,14 @@ You can add intermediate columns to track your bug status on the board. You can
 
 - [Add columns to your Kanban board](../boards/add-columns.md)
 - [Customize a sprint Taskboard](../sprints/customize-taskboard.md)
-- [Kanban board change queries](../queries/query-by-workflow-changes.md#query-changes-to-a-kanban-board)
+- [Kanban board change queries](../queries/query-by-workflow-changes.md#kanban-query-fields)
 
 ::: moniker-end
 
 ::: moniker range="< azure-devops-2020"
 
 - [Add columns to your Kanban board](../boards/add-columns.md)
-- [Kanban board change queries](../queries/query-by-workflow-changes.md#query-changes-to-a-kanban-board)
+- [Kanban board change queries](../queries/query-by-workflow-changes.md#kanban-query-fields)
 
 ::: moniker-end
 

Diff for: docs/boards/backlogs/remove-delete-work-items.md

@@ -196,6 +196,7 @@ Deleted work items won't appear in your backlogs, boards, or queries. Deleted it
 
 
 <a id="restore" />
+<a id="restore-or-destroy-work-items" />
 <a id="restore-or-permanently-delete-work-items" />
 
 ::: moniker range=">= tfs-2015"  

Diff for: docs/boards/backlogs/work-item-template.md

@@ -363,13 +363,11 @@ You manage templates from  team settings. All templates are defined for a team.
 
 ::: moniker-end
 
-
+<a id="define-template" />
 ::: moniker range=">= tfs-2017"
 
 ### Create a work item template 
 
-<a id="define-template" />
-
 1. From the work item type page, choose the ![green plus icon](../media/icons/green_plus_icon.png) **New template** to create a template from scratch.  
     
     <img src="media/wi-templates-new-template.png" alt="Add a user story template" />  
@@ -720,10 +718,8 @@ For example, the following syntax specifies a work item task with title *TaskTit
 
 You can save the URL as a text file or add the URL to a dashboard or web page as a hyperlink. 
 
-
-::: moniker range=">= tfs-2015"
-
 <a id="markdown-widget"> </a>
+::: moniker range=">= tfs-2015"
 
 ## Add a template link to a team dashboard   
 

Diff for: docs/boards/includes/activated-resolved-by-fields.md

@@ -6,11 +6,10 @@ ms.topic: include
 ms.date: 04/08/2021
 ---
 
+<a id="activated-resolved-fields" />
 
 ::: moniker range=">= azure-devops-2020"
 
-<a id="activated-resolved-fields" />
-
 ### Activated By/Date and Resolved By/Date fields 
 
 The system updates these fields&mdash;**Activated By**, **Activated Date**, **Resolved By**, and **Resolved Date**&mdash;when a change occurs based on corresponding workflow category states. When the workflow state changes to a *Proposed* state category, **Activated By** and **Activated Date** are updated. When the workflow state changes to a *Resolved* state category, **Resolved By** and **Resolved Date** are updated. 

Diff for: docs/boards/includes/discussion-tip-azure-devops.md

@@ -8,6 +8,8 @@ ms.date: 07/09/2020
 ---
 
 
+<a id="capture-comments-in-the-discussion-section" />
+
 ## Capture comments in the Discussion section 
 
 Use the **Discussion** section to add and review comments made about the work being performed. 

Diff for: docs/boards/includes/discussion-tip.md

@@ -8,7 +8,7 @@ ms.date: 07/09/2020
 ---
 
 <a id="discussion" />
-
+<a id="capture-comments-in-the-discussion-section" />
 ::: moniker range=">= tfs-2017" 
 
 ## Capture comments in the Discussion section 

Diff for: docs/boards/queries/add-tags-to-work-items.md

@@ -214,9 +214,9 @@ Requires TFS 2015.1 or later version.
 
 ::: moniker-end   
 
-::: moniker range="azure-devops"
 
 <a id="group-by-tags"></a> 
+::: moniker range="azure-devops"
 
 ## Chart work items and group by tags
 

Diff for: docs/boards/queries/link-work-items-support-traceability.md

@@ -251,9 +251,9 @@ See the following articles for more information:
 - [Auto complete work items with pull requests](../work-items/auto-complete-work-items-pull-requests.md).
 ::: moniker-end
 
-::: moniker range=">= tfs-2017"
 
 <a id="git-code-development" /> 
+::: moniker range=">= tfs-2017"
 
 ## Work items linked to Git code development  
 

Diff for: docs/boards/queries/query-by-workflow-changes.md

@@ -359,9 +359,9 @@ To list work items that have changed state within a specific date range, you can
 > ![Screenshot of Query Editor to query on State Change Date and State fields](media/workflow/query-state-change-date.png)
 
 
-
-
-<a id="kanban_query_fields">  </a>
+<a id="query-changes-to-a-kanban-board" />
+<a id="kanban-query-fields" />
+<a id="kanban_query_fields" />
 
 ::: moniker range=">= tfs-2015"
 
@@ -799,11 +799,9 @@ You can use the following fields to filter your queries or build reports. Some o
    :::column-end:::
 :::row-end:::
 
+<a id="sync">  </a>
 ::: moniker range="azure-devops"
 > [!NOTE]  
-> 
-> <a id="sync">  </a>
->
 > 1. See [Date and Identity fields](#date-identity).  
 > 2.  By default, the server synchronizes system-defined person-name or Identity-based fields with Active Directory or Azure Active Directory. These fields include: **Activated By**, **Assigned To**, **Closed By**, **Created By**, and **Resolved By**. You can grant access to a project by adding security groups that you created in AD or Azure AD or by adding accounts to existing or custom groups defined from the collection setting **Security** page. See set up [Active Directory or Azure Active Directory](../../organizations/security/about-permissions.md#aad). 
 > 3. See [Activated By/Date and Resolved By/Date fields](#activated-resolved-fields).   

Diff for: docs/boards/queries/titles-ids-descriptions.md

@@ -138,10 +138,9 @@ You can find work items that have an undefined field value by using the equals o
 
 To list work items based on a field that isn't blank, use the not operator (<>) and leave the Value blank.
 
-
-::: moniker range=">= azure-devops-2019"
-
 <a id="empty"/>
+<a id="empty-or-not-empty-html-field-queries"/>
+::: moniker range=">= azure-devops-2019"
 
 ## Empty or not empty HTML field queries
 
@@ -183,11 +182,8 @@ The default assignments of work item types to each category are listed below for
 
 Each team can determine if the Bug work item type appears in either the Requirement or Task category. See [Show bugs on backlogs and boards](../../organizations/settings/show-bugs-on-backlog.md). You can add custom work item types to a backlog. For details, see [Add or modify a work item type, Add a custom WIT to a backlog or board](../../reference/add-modify-wit.md). 
 
-
-::: moniker range=">= tfs-2017"
-
-
 <a id="following" />
+::: moniker range=">= tfs-2017"
 
 ## Query for work items that you're following
 
@@ -200,10 +196,8 @@ For example, the following query shows how to query across all projects for acti
 
 ::: moniker-end 
 
-
-::: moniker range=">= tfs-2018"
-
 <a id="recent-macros" />
+::: moniker range=">= tfs-2018"
 
 ## Query for recent work item activity
 

Diff for: docs/organizations/projects/about-projects.md

@@ -118,9 +118,9 @@ To create or list projects, see [Create a project](create-project.md)
 
 ::: moniker-end
 
-::: moniker range="azure-devops"
 
 <a id="project-scoped-user-group" /> 
+::: moniker range="azure-devops"
 
 ## Limit user visibility for projects using the Project-Scoped Users group 
 

Diff for: docs/organizations/projects/create-project.md

@@ -584,7 +584,7 @@ From Team Explorer, you can view a list of projects by connecting to an organiza
 
 
 <a id="add-a-repository" />
-
+<a id="add-a-repository-to-your-project" />
 ::: moniker range=">= tfs-2015"
 
 ## Add a repository to your project

Diff for: docs/organizations/security/lookup-organization-owner-admin.md

@@ -32,10 +32,8 @@ To determine what level a permission is defined, see the [Permissions lookup gui
 
 ::: moniker-end  
 
-
-::: moniker range="azure-devops"
-
 <a name="find-owner"></a>
+::: moniker range="azure-devops"
 
 ## Look up the organization owner 
 

Diff for: docs/organizations/security/namespace-reference.md

@@ -398,7 +398,7 @@ The following table describes the namespaces that manage project-level permissio
       Token to secure permissions for each project in your organization.  
       `$PROJECT:vstfs:///Classification/TeamProject/PROJECT_ID`.  
       Assume you have a project named `Test Project 1`.  
-      You can get the project ID for this project by using the [`az devops project show` command](../projects/create-project.md#show-project).  
+      You can get the project ID for this project by using the [`az devops project show` command](../projects/create-project.md).  
       `az devops project show --project "Test Project 1"`  
       The command returns a project-id, for example, `xxxxxxxx-a1de-4bc8-b751-188eea17c3ba`.  
       Therefore, the token to secure project-related permissions for `Test Project 1` is:  

Diff for: docs/organizations/security/set-permissions-access-work-tracking.md

@@ -223,10 +223,8 @@ To manage permissions for a query or query folder, you must be the creator of th
 
 For details, see [Set permissions on a shared query or query folder](../../organizations/security/set-permissions-access-work-tracking.md). To learn more about queries, see [Create managed queries to list, update, or chart work items](../../boards/queries/about-managed-queries.md).
 
-
-::: moniker range=">= tfs-2017"  
-
 <a id="tags" /> 
+::: moniker range=">= tfs-2017"  
 
 ## Set permissions on work item tags 
 

Diff for: docs/organizations/security/troubleshoot-permissions.md

@@ -242,6 +242,9 @@ For more information, see [Use TFSSecurity to manage groups and permissions for
 
 ::: moniker-end
 
+
+<a id="group-rules-with-lesser-permissions" />
+
 ::: moniker range=" azure-devops"
 
 ## Group rules with lesser permissions

Diff for: docs/organizations/settings/manage-teams.md

@@ -271,6 +271,8 @@ Similar to Kanban boards, each sprint Taskboard can be customized to support inf
 
 :::image type="content" source="media/configure-sprint-taskboard.png" alt-text="Screenshot of Taskboard selection.":::
 
+
+<a id="add-and-manage-team-dashboards" /> 
 ::: moniker range=">= tfs-2017" 
 
 ## Add and manage team dashboards   

Diff for: docs/reference/add-modify-field.md

@@ -79,8 +79,10 @@ To add rules or add a custom field, export, edit, and then import the WIT defini
 
 Any field that you want to use to track data must be added to the WIT definition file. This is true for all but system fields (fields whose reference name start with **System.**). All System fields are defined for all WITs, whether or not you include them in WIT definition. To learn more about each field, see [Work item field index](../boards/work-items/guidance/work-item-field.md).
 
-::: moniker range=">= tfs-2017"
 <a id="boolean-field">  </a>
+
+::: moniker range=">= tfs-2017"
+
 ## Add a checkbox or Boolean field 
 ::: moniker-end
 

Diff for: docs/report/dashboards/charts.md

@@ -352,8 +352,8 @@ To add other types of charts, such as test results and build summary charts, see
 > For TFS 2013 and TFS 2015, you can pin charts to the team homepage. For TFS 2015.1 and later versions, you can add charts to [multiple team dashboards](dashboards.md) and get access to the [widget catalog](widget-catalog.md). 
 ::: moniker-end
 
-::: moniker range=">= tfs-2015"
 <a id="add-chart-widget"></a> 
+::: moniker range=">= tfs-2015"
 
 ## Add a chart widget to a dashboard   
 

Diff for: docs/repos/git/pull-requests.md

@@ -679,10 +679,8 @@ You can attach files, including images, to your PR during or after creation. Sel
 ![Screenshot that shows attaching files to the P R description during creation.](media/pull-requests/attachment.png)
 
 ::: moniker-end
-
-::: moniker range=">=azure-devops-2019"
-
 <a name="change-the-target-branch-of-a-pull-request"></a>
+::: moniker range=">=azure-devops-2019"
 
 ## Change the target branch of an active pull request