Merge pull request #2416 from MicrosoftDocs/users/kaelli/new-git-tool…

…-other

user-guide toc changes

docs/boards/backlogs/work-item-template.md

@@ -1,14 +1,14 @@
 ---
 title: Use work item templates to update stories, & more
 titleSuffix: Azure Boards   
-description: Add and manage work item templates to pre-populate fields in work item forms in Azure DevOps, Team Foundation Server, and Visual Studio
+description: Add and manage work item templates to pre-populate fields in work item forms in Azure DevOps and Visual Studio
 ms.technology: devops-agile
 ms.assetid: 9b575c05-16f3-4027-aa5a-67b017a0089d
 ms.author: kaelli
 author: KathrynEE
 ms.topic: conceptual
-monikerRange: '>= tfs-2013'
-ms.date: 07/09/2020
+monikerRange: '<= azure-devops'
+ms.date: 11/11/2020
 ---
 
 # Use templates to add and update work items 

docs/boards/includes/note-git-vs-github-connect.md

@@ -0,0 +1,12 @@
+---
+ms.technology: devops-code-git 
+ms.prod: devops
+ms.manager: mijacobs
+ms.author: kaelli
+author: KathrynEE
+ms.topic: include
+ms.date: 11/04/2020
+---
+
+> [!NOTE]   
+> The **Work Items** page is only supported when connected to an Azure Repos Git or TFVC repository. When you connect to a GitHub or other Git repository, the **Work Items** and **Builds** pages don't appear.  

docs/boards/includes/note-new-git-tool-boards.md

@@ -0,0 +1,12 @@
+---
+ms.technology: devops-code-git 
+ms.prod: devops
+ms.manager: mijacobs
+ms.author: kaelli
+author: KathrynEE
+ms.topic: include
+ms.date: 11/04/2020
+---
+
+> [!NOTE]   
+> Visual Studio 2019 now includes a new Git tool that provides an improved experience when connecting to a Git repository. When you enable this tool, the Team Explorer tool is effectively disabled when connected to a Git repository.  You can acquire the new tool by downloading [Visual Studio 2019 version 16.6](/visualstudio/releases/2019/release-notes-v16.6). To enable and use the new tool, see [New Git experience in Visual Studio (Preview)](/visualstudio/ide/git-with-visual-studio).  

docs/boards/includes/prerequisites-work-items.md

@@ -13,9 +13,8 @@ ms.date: 07/09/2020
 
 * You must connect to a project. If you don't have a project yet, [create one](../get-started/sign-up-invite-teammates.md). 
 * You must be added to a project as a member of the **Contributors** or **Project Administrators** security group. To get added, [Add users to a project or team](../../organizations/security/add-users-team-project.md). 
-* To add or modify work items, you must be granted **Stakeholder** access or higher. For details, see [About access levels](../../organizations/security/access-levels.md).
 * To view or modify work items, you must have your **View work items in this node** and **Edit work items in this node** permissions set to **Allow**. By default, the **Contributors** group has this permission set. To learn more, see [Set permissions and access for work tracking](../../organizations/security/set-permissions-access-work-tracking.md).  
-* To create new tags to add to work items, you must have **Basic** access or higher and have the project-level **Create new tag definition** permissions set to **Allow**. By default, the **Contributors** group has this permission set. Even if the permission is explicitly set for a **Stakeholder**, they won't have permission to add new tags, as they are prohibited through their access level. 
+* To add new tags to add to work items, you must have **Basic** access or higher and have the project-level **Create new tag definition** permissions set to **Allow**. By default, the **Contributors** group has this permission set. Even if the permission is explicitly set for a **Stakeholder**, they won't have permission to add new tags, as they are prohibited through their access level. 
 
 
 ::: moniker-end
@@ -24,8 +23,7 @@ ms.date: 07/09/2020
 
 * You must connect to a project. If you don't have a project yet, [create one](../../organizations/projects/create-project.md).
 * You must be added to a project as a member of the **Contributors** or **Project Administrators** security group. To get added, [Add users to a project or team](../../organizations/security/add-users-team-project.md). 
-* To add or modify work items, you must be granted **Stakeholder** access or higher. For details, see [About access levels](../../organizations/security/access-levels.md).
 * To view or modify work items, you must have your **View work items in this node** and **Edit work items in this node** permissions set to **Allow**.  By default, the **Contributors** group has this permission set. To learn more, see [Set permissions and access for work tracking](../../organizations/security/set-permissions-access-work-tracking.md).  
-* To create new tags to add to work items, you must have **Basic** access or higher and have the project-level **Create new tag definition** permissions set to **Allow**. By default, the **Contributors** group has this permission set. Even if the permission is explicitly set for a **Stakeholder**, they won't have permission to add new tags, as they are prohibited through their access level. 
+* To add new tags to add to work items, you must have **Basic** access or higher and have the project-level **Create new tag definition** permissions set to **Allow**. By default, the **Contributors** group has this permission set. Even if the permission is explicitly set for a **Stakeholder**, they won't have permission to add new tags, as they are prohibited through their access level. 
 
 ::: moniker-end

docs/boards/queries/history-and-auditing.md

@@ -309,15 +309,12 @@ All
     ```
 
 ## Related articles
-To learn more about creating and saving queries, see also: 
+
 
 - [Query editor](using-queries.md)
 - [Query fields, operators, and macros](query-operators-variables.md)   
 - [Query by date or current iteration](query-by-date-or-current-iteration.md)
-
-
-### Get history programmatically
-See [Work item tracking](/rest/api/azure/devops/wit/)  for ways to extract history information programmatically.  
+
 
 [!INCLUDE [temp](../includes/rest-apis-queries.md)]
 

docs/boards/work-items/set-work-item-experience-vs.md

@@ -8,7 +8,7 @@ ms.assetid: EBDE0739-FAE6-4BEA-8F59-E9D20AFE5FE8
 ms.author: kaelli
 ms.topic: quickstart
 monikerRange: '>= azure-devops-2019'
-ms.date: 07/09/2020
+ms.date: 11/11/2020
 ---
 
 # Set the Work Items experience in Visual Studio 2019
@@ -59,7 +59,10 @@ Each view supports the following tasks:
 
 To learn more about **Options**, see [Options Dialog Box (Visual Studio)](/visualstudio/ide/reference/options-dialog-box-visual-studio).
 
+## New Git tool experience
 
+Visual Studio 2019 now includes a new Git tool that provides an improved experience when connecting to a Git repository. When you enable this tool, the Team Explorer tool is effectively disabled when connected to a Git repository. You can acquire the new tool by downloading [Visual Studio 2019 version 16.6](/visualstudio/releases/2019/release-notes-v16.6). To enable and use the new tool, see [New Git experience in Visual Studio (Preview)](/visualstudio/ide/git-with-visual-studio).  
 
 ## Related articles
+
 - [View and add work items using the Work Items page](view-add-work-items.md)

docs/boards/work-items/view-add-work-items.md

@@ -12,12 +12,12 @@ ms.author: kaelli
 author: KathrynEE
 ms.topic: quickstart
 monikerRange: '>= azure-devops-2019'
-ms.date: 07/09/2020
+ms.date: 11/11/2020
 ---
 
 # View and add work items using the Work Items page  
 
-**Azure Boards | Azure DevOps Server 2020 |Azure DevOps Server 2019 | Visual Studio 2019** 
+**Azure Boards | Azure DevOps Server 2020 | Azure DevOps Server 2019 | Visual Studio 2019** 
 
 
 View work items that you created or are assigned to you. The **Work Items** page provides several personalized pivots and filter functions to streamline listing work items. Use this page to quickly find work items defined across teams within a project. 
@@ -40,37 +40,40 @@ You can start viewing and adding work items once you connect to a project.
 > [!div class="mx-imgBorder"]  
 > ![Open Boards>Work Items](media/view-add/open-work-items-agile.png)
 
-::: moniker range="azure-devops-2019"
-
-> [!NOTE]   
-> The new Work Items experience is available when you connect to a GitHub repository. If you connect to a TFVC repository, you'll continue to see the legacy query-focused experience. 
-
-::: moniker-end
-
 
 #### [Visual Studio 2019](#tab/visual-studio/)
 
-Open Visual Studio 2019, Team Explorer, and then choose **Work Items**. 
+Open Visual Studio 2019, Team Explorer, and then choose **Work Items**. To switch between the **Work Items** (default) view and the legacy view, see [Set the Work Items experience in Visual Studio 2019](set-work-item-experience-vs.md).  
+
+[!INCLUDE [temp](../includes/note-git-vs-github-connect.md)] 
 
 > [!div class="mx-imgBorder"]  
 > ![Visual Studio, Team Explorer, Choose Work Items](media/view-add/open-work-items-vs-te-complete.png) 
 
-
 If you don't see the **Work Items** option, you need to connect to a project and not just a repository. From the Connect to a Project dialog. Use **CTRL-Shift** to select your options and then choose **Connect**.
 
 > [!div class="mx-imgBorder"]  
 > ![Connect to a Project dialog, connect to a Project and Git repository](media/view-add/connect-to-a-project-and-github.png)
 
+
+::: moniker range="azure-devops-2019"
+
+> [!NOTE]   
+> The new **Work Items** experience is available when you connect to a Azure Repos Git repository. If you connect to a TFVC repository, you'll continue to see the legacy query-focused experience.  
+
+::: moniker-end
+
+
 #### [Azure DevOps CLI](#tab/azure-devops-cli/)
 
-There is no [**az boards**](/cli/azure/ext/azure-devops/boards) command that opens the Work Items page at this time. The Azure DevOps CLI commands are only valid for Azure DevOps Services (cloud service).
+There is no [**az boards**](/cli/azure/ext/azure-devops/boards) command that opens the **Work Items** page at this time. The Azure DevOps CLI commands are valid for Azure DevOps Services and Azure DevOps Server 2020.
 
 * * *
 
 > [!NOTE]    
-> Depending on the process chosen when the project was created—[Agile](guidance/agile-process-workflow.md), [Scrum](guidance/scrum-process-workflow.md), or [CMMI](guidance/cmmi-process-workflow.md)—the types of work items you can create will differ. For example, backlog items may be called user stories (Agile), product backlog items (Scrum), or requirements (CMMI). All three are similar: they describe the customer value to deliver and the work to be performed.
+> Depending on the process chosen when the project was created—[Agile](guidance/agile-process-workflow.md), [Basic](../get-started/plan-track-work.md), [Scrum](guidance/scrum-process-workflow.md), or [CMMI](guidance/cmmi-process-workflow.md)—the types of work items you can create differ. For example, backlog items may be called user stories (Agile), issues (Basic), product backlog items (Scrum), or requirements (CMMI). All three are similar: they describe the customer value to deliver and the work to be performed.
 >
-> For an overview of all three processes, see [Choose a process](../work-items/guidance/choose-process.md). 
+> For an overview of these processes, see [Choose a process](../work-items/guidance/choose-process.md). 
 
 
 ## View work items
@@ -313,6 +316,5 @@ Use the following three controls to manage your views in the web portal.
 - [Keyboard shortcuts](../../project/navigation/keyboard-shortcuts.md)
 - [Work across projects](../../project/navigation/work-across-projects.md)
 
-> [!NOTE]
-> You can create and manage work items from the command line or scripts using the [Azure DevOps CLI](/cli/azure/ext/azure-devops/?view=azure-cli-latest&preserve-view=true).
+
 

docs/organizations/projects/create-project.md

@@ -628,4 +628,6 @@ From the admin context of the web portal, you can add additional repositories to
 - [Get Started with Azure Repos and Visual Studio](../../repos/git/gitquickstart.md)
 - [Git and Azure Repos](../../repos/git/index.yml)
 - [Team Foundation version control](../../repos/tfvc/index.yml)
-- [Get started as an administrator](../../user-guide/project-admin-tutorial.md)
+- [Get started as an administrator](../../user-guide/project-admin-tutorial.md)
+- [Navigate in Visual Studio Team Explorer](../../user-guide/work-team-explorer.md)
+- [New Git experience in Visual Studio (Preview)](/visualstudio/ide/git-with-visual-studio)

docs/organizations/projects/rename-project.md

@@ -237,3 +237,10 @@ The reporting and SharePoint server administrator can manually run these jobs to
 
 ::: moniker-end
 
+
+## Related articles
+
+- [Git and Azure Repos](../../repos/git/index.yml)
+- [Team Foundation version control](../../repos/tfvc/index.yml)
+- [Navigate in Visual Studio Team Explorer](../../user-guide/work-team-explorer.md)
+- [New Git experience in Visual Studio (Preview)](/visualstudio/ide/git-with-visual-studio)

docs/organizations/public/clone-git-repo-public.md

@@ -49,6 +49,8 @@ Before you can clone the repo from a public project, you'll need the clone URL.
 
 ### Clone using Visual Studio and Team Explorer
 
+[!INCLUDE [temp](../../repos/git/includes/note-new-git-tool.md)] 
+
 1. In Team Explorer, (1) open up the **Connect** page by selecting the **Connect** icon. (2) Choose **Clone** under **Local Git Repositories**, (3) enter the clone URL, verify your local folder in which to clone, and (4) select the **Clone** button.
 
    ![Connecting to Azure DevOps](media/clone-git-repo-public/clone-vs.png)