Copy items to another workspace

You can copy or move items to another workspace within the same space.

In this topic:

Copy an item to another workspace

You can copy backlog items, manual tests, and Gherkin tests to another workspace within the same space. You can copy one backlog item or test at a time.

To copy a backlog item or test to another workspace:

1. Prerequisites: You must have the following permissions:

   • Create permission for the item type on the target workspace.

   • Copy to Different Workspace permission for the item type on both source and target workspaces.

   For details, see Permission categories and types.

2. Open the backlog item or test that you want to copy.

3. In the item's Details tab, click More and select Copy to Different Workspace.

4. Choose the target workspace and click Copy.

   After the copy completes, a message displays with a link to the new item in the target workspace.

Values and attributes of copied items

The new item is initiated as follows.

Field	Description
Phase	The phase is reset to New.
Comments	A comment is added containing a link to the original item in the source workspace.
Author	This is set to the user who performed the copy action.
Detected By	This field in defects is copied from the original item. Make sure that the same user exists in the destination workspace.
History tab	The item is created with a clear History tab.

Field values and attributes are copied to the new item as follows.

Status	Details
Copied	The new item includes values for the fields that are defined at the shared space level. This applies to both system and custom fields. In addition, the following are copied: Attachments Backlog items: Tasks Tests: Data tables and sets, the current version
Not copied	Values are not copied where the value is defined at the workspace level, such as local application modules, programs, teams, and releases. In addition, the following are not copied: Comments, Data access categories Tests: Runs, previous versions, automation status

Back to top

Move a backlog item to a different workspace

You can move backlog items from one workspace to another in the same space. You can move one backlog item at a time.

To move a backlog item to another workspace:

1. Prerequisite: You must have the Move to Different Workspace permission for the item type on both source and target workspaces. For details, see Permission categories and types.

2. In the backlog item's Details tab, click More and select Move to Different Workspace.

3. In the Move to Different Workspace dialog box, select the target workspace, and then click Move.

   Refresh the grid in the target workspace to view the change.

Backlog item details that are moved

The following table lists the backlog item details that are moved between workspaces and any restrictions.

Field	Description
Common fields	Fields vary depending on the entities that the workspaces share. For example: The Owner field is saved only if the user is part of the new workspace. Otherwise, it is left blank. The Author field is saved only if the user is part of the new workspace. Otherwise, the user who is moving the backlog item is the author. Phases that exist in the original workspace but do not exist in the new workspace are replaced with the master phase. For details, see Master phase. Releases associated with the shared space are moved, while releases associated with the workspace are not.
Attachments, comments, history	Moved to the new workspace.
User-defined fields (UDFs)	Moved if defined at the shared space level and are common to both workspaces.
Associations	Associations with features and backlog items cannot be moved to the new workspace. All associations are removed.

Back to top