Merged PR 360326: Added Preview Notes to Migration to Inherited Docs

added preview notes changed TOC
PBoraMSFT · Jul 2, 2018 · 5442fc7 · 5442fc7
1 parent 43c8769
commit 5442fc7
Show file tree

Hide file tree

Showing 5 changed files with 23 additions and 19 deletions.
diff --git a/docs/organizations/settings/work/change-process-from-hosted-to-inherited.md b/docs/organizations/settings/work/change-process-from-hosted-to-inherited.md
@@ -16,16 +16,17 @@ ms.date: 05/30/2018
 
 [!INCLUDE [temp](../../../_shared/version-vsts-only.md)]
 
+> [!NOTE]  
+> This feature is currently in private preview. If you are interested in changing your processes from Hosted XML to Inherited, please email us at [vstsprivatepreview@microsoft.com](mailto:vstsprivatepreview@microsoft.com) to get the feature turned on in your account(s).
+
 Once you've [upgraded your Hosted XML process to an inherited process](upgrade-hosted-to-inherited.md), you can change the project(s) from the Hosted XML process to the inherited process. You change a project from a Hosted XML process to its derived inherited process to start customizing the process through the user interface.  
 
-> [!IMPORTANT]  
+> [!CAUTION] 
 > Choosing to upgrade a team project from a Hosted XML process model to an inherited process is an irreversible operation. Before you change the process of an existing project from Hosted XML to the upgraded inherited process, review [Supported upgrade operations when moving from Hosted XML process to inherited process](upgrade-support-hosted-to-inherited.md) to understand which customizations are preserved and which are not before you change the process of a project from Hosted XML to an inherited process. Also, [create a test project](upgrade-hosted-to-inherited.md#verify) to verify the customizations preserved or reapplied to a process.
 
-
 ## Prerequisites 
 - You must be a member of the Project Administrators group for the project you want to change, or a member of the Project Collection Administrators group.
 
-
 <a id="open-process-wit">  </a>
 ## Open Settings>Process hub
 

diff --git a/docs/organizations/settings/work/upgrade-hosted-to-inherited.md b/docs/organizations/settings/work/upgrade-hosted-to-inherited.md
@@ -16,6 +16,9 @@ ms.date: 05/30/2018
 
 [!INCLUDE [temp](../../../_shared/version-vsts-only.md)]
 
+> [!NOTE]  
+> This feature is currently in private preview. If you are interested in changing your processes from Hosted XML to Inherited, please email us at [vstsprivatepreview@microsoft.com](mailto:vstsprivatepreview@microsoft.com) to get the feature turned on in your account(s).
+
 Upgrading your Hosted XML process to the Inheritance process model allows you to manage customizations through the user interface versus XML definition files. The inherited process supports the set of customizations described here [About process customization and inherited processes](inheritance-process-model.md). 
 
 Before you upgrade a Hosted XML process, we recommend that you review [Supported upgrade operations when moving from Hosted XML process to inherited process](upgrade-support-hosted-to-inherited.md). 

diff --git a/docs/organizations/settings/work/upgrade-support-hosted-to-inherited.md b/docs/organizations/settings/work/upgrade-support-hosted-to-inherited.md
@@ -18,6 +18,9 @@ ms.date: 05/30/2018
 
 [!INCLUDE [temp](../../../_shared/version-vsts-only.md)]
 
+> [!NOTE]  
+> This feature is currently in private preview. If you are interested in changing your processes from Hosted XML to Inherited, please email us at [vstsprivatepreview@microsoft.com](mailto:vstsprivatepreview@microsoft.com) to get the feature turned on in your account(s).
+
 <a id="hosted-xml-process-model">  </a>
 
 Upgrading a Hosted XML process model to an inherited process  provides the convenience of customizing your work tracking system through the user interface. For an overview of supported customizations available to you with the Inheritance process, see [About process customization and inherited processes](inheritance-process-model.md). 

diff --git a/docs/work/customize/import-process/import-process.md b/docs/work/customize/import-process/import-process.md
@@ -6,7 +6,8 @@ ms.technology: devops-agile
 ms.prod: devops
 ms.assetid: AF7ABA0F-D3E8-48CA-9164-ABC966BAAA77
 ms.manager: douge
-ms.author: kaelliauthor: KathrynEE
+ms.author: kaelli
+author: KathrynEE
 monikerRange: 'vsts'
 ms.date: 03/20/2018
 ---
@@ -40,14 +41,13 @@ Import process supports the following scenarios:
 *   [Import a new process created from an existing exported process](#import-process)  
 *   [Import an update to an existing process, and have all projects using that process be updated](#update-process)  
 
-
-
 <a id="import-from-TFS">  </a>
 ## Import a process from an on-premises TFS 
 
-Your first step in migrating team projects that contain custom work tracking objects is to import the process to VSTS.
+These steps can be followed if you want to test your process in TFS to see if it works in VSTS.
+
 In Team Foundation Server, each project has its own copy of process so careful consideration needs to be made as to which processes should exist for your organization.
-Migration to VSTSis a great time to think about process alignment across your organization and reducing the number of variants of that centralized process.  
+Migration to VSTS is a great time to think about process alignment across your organization and reducing the number of variants of that centralized process.  
 
 1.  Run the [process export script](customize-process.md#open-process-wit) to generate a process for a given team project.   
 
@@ -61,11 +61,6 @@ Migration to VSTSis a great time to think about process alignment across your or
 
 6.  Using the imported process(es), create team projects on VSTS for each you want to migrate. 
 
-    With the project created, you can now migrate the project data to VSTS using the [TFS Database Import Service](https://aka.ms/tfsimport).
-
-
-
-
 <a id="open-process-wit">  </a>
 ### Open Process in the admin context
 

diff --git a/docs/work/customize/toc.yml b/docs/work/customize/toc.yml
@@ -71,18 +71,20 @@
   - name: Hosted XML process model
     href: hosted-xml-process-model.md
     items:
-    - name: Supported upgrade operations
-      href: ../../organizations/settings/work/upgrade-support-hosted-to-inherited.md?toc=/vsts/work/customize/toc.json&bc=/vsts/work/customize/breadcrumb/toc.json
-    - name: Upgrade a Hosted XML process to Inheritance
-      href: ../../organizations/settings/work/upgrade-hosted-to-inherited.md?toc=/vsts/work/customize/toc.json&bc=/vsts/work/customize/breadcrumb/toc.json
-    - name: Change a project from Hosted XML to Inheritance
-      href: ../../organizations/settings/work/change-process-from-hosted-to-inherited.md?toc=/vsts/work/customize/toc.json&bc=/vsts/work/customize/breadcrumb/toc.json
     - name: Customize a Hosted XML process
       href: import-process/customize-process.md?toc=/vsts/work/customize/toc.json&bc=/vsts/work/customize/breadcrumb/toc.json
     - name: Import a process
       href: import-process/import-process.md?toc=/vsts/work/customize/toc.json&bc=/vsts/work/customize/breadcrumb/toc.json
     - name: Customize form layout
       href: customize-wit-form.md
+    - name: Migrate Hosted XML to inherited (Preview)
+      items:
+      - name: Supported upgrade operations
+        href: ../../organizations/settings/work/upgrade-support-hosted-to-inherited.md?toc=/vsts/work/customize/toc.json&bc=/vsts/work/customize/breadcrumb/toc.json
+      - name: Upgrade a Hosted XML process to Inheritance
+        href: ../../organizations/settings/work/upgrade-hosted-to-inherited.md?toc=/vsts/work/customize/toc.json&bc=/vsts/work/customize/breadcrumb/toc.json
+      - name: Change a project from Hosted XML to Inheritance
+        href: ../../organizations/settings/work/change-process-from-hosted-to-inherited.md?toc=/vsts/work/customize/toc.json&bc=/vsts/work/customize/breadcrumb/toc.json
   - name: On-premises XML process model
     href: on-premises-xml-process-model.md
     items: