Merge pull request #8332 from MicrosoftDocs/users/dahellem/copy-clone-1

Updating copy and clone done to reflect deprecation of clone feature

Author: prmerger-automator[bot]

docs/boards/backlogs/copy-clone-work-items.md

@@ -15,13 +15,24 @@ ms.date: 09/09/2024
 # Copy or clone work items and more
 
 [!INCLUDE [version-lt-eq-azure-devops](../../includes/version-lt-eq-azure-devops.md)] 
+	
+::: moniker range="<azure-devops"
 
 There are two types of copy functions you can use:
 
 - **Copy or clone a single work item:** To duplicate a single work item, use the "Create copy of a work item" feature. Depending on the options you choose, this process can be considered either a [copy or a clone](#copy-or-clone-a-work-item).
 - **Copy a list of work items:** To copy a list of work items, multi-select a list of work items and use the "Copy as HTML" or "Copy to clipboard" feature.
 
-[!INCLUDE [temp](../includes/image-differences.md)]
+::: moniker-end
+
+::: moniker range="azure-devops"
+
+There are two types of copy functions you can use:
+
+- **Copy a single work item:** To duplicate a single work item, use the "Create copy of a work item" feature.
+- **Copy a list of work items:** To copy a list of work items, multi-select a list of work items and use the "Copy as HTML" or "Copy to clipboard" feature.
+
+::: moniker-end
 
 ## Prerequisites
 
@@ -31,14 +42,21 @@ There are two types of copy functions you can use:
 
 ## Copy or clone a work item
 
+::: moniker range="azure-devops"
+
+> [!IMPORTANT]
+> The option to clone a work item is not longer available in the Azure DevOps Service. You can use the Copy option instead.
+
+::: moniker-end
+
 **Copy** a work item to create a new work item with a new ID and prepopulated fields from the original. You can modify the fields as needed. A related link to the original work item and any parent link are copied over, but history and attachments are not.
 
+::: moniker range="<azure-devops"
+
 **Clone** a work item to create an exact copy of an existing work item, including all fields and attachments, but with a new ID. Cloning is useful when no field modifications are needed.
 
 In summary, **copy** a work item to adjust prepopulated values, and **clone** a work item to create an exact duplicate.
 
-::: moniker range="< azure-devops"
-
 > [!NOTE]
 > Some fields might get copied depending on your on-premises version and customizations. If the work item type you clone lacks a state transition rule to clear the *Closed By* field when the *State* is **New** or **Active**, that field gets copied. Current system out-of-box templates include this rule.
 
@@ -69,9 +87,6 @@ In summary, **copy** a work item to adjust prepopulated values, and **clone** a
 
 ::: moniker-end
 
-> [!TIP]
-> Copied or cloned work items always have a higher ID than the original work items.
-
 ## Change the work item type
 
 If you have a large number of work items whose type you want to change, use [Change work item type](move-change-type.md). If the **Change work item type** option isn't available to you, you can export a set of work items using Excel or CSV, copy them to a new list, and reimport them by specifying a different work item type. See [Bulk add or modify work items with Excel](../backlogs/office/bulk-add-modify-work-items-excel.md) or [Import or update work items in bulk by using CSV files](../queries/import-work-items-from-csv.md).