Only available for

Cloning a release package that has been released or rejected is a way to create a new release package once changes have been made to a part or parts within a workspace.

Clone allows you to use the existing release package as a starting template for the new package.

In order to clone release packages, you need the appropriate permissions on the document. You also must be viewing the workspace on the branch from which the previous release package was created. If you are not in the workspace of that branch, you will not see the option to Clone the release package.

Steps

To clone a released or rejected release package:

1. Open the workspace on the branch from which the previous release package was created.
2. Open the Versions and history panel on the left side of the graphics area.
3. With the top branch selected, right-click on the name of the release version to access the context menu.
4. In the context menu, hover over Releases to display the releases available.
5. Select the release to clone:

   

   Above, the blue highlighting indicates that B1 is the workspace currently being viewed; the release candidate (rel-candidate-1) is being accessed from the version rel-candidate-1, and the release package has been previously rejected.

   The Review Release dialog opens.

   

6. Click Clone to begin recreating a release package from the current workspace.

   If the Clone button is absent, verify which workspace you are currently viewing and open the one on the branch that the previous release was created from.

7. When the Create Release candidate dialog opens, the parts previously released are now replaced with the parts in the workspace, most likely updated per the requirements of the release manager.

   You can, of course, make any changes necessary: add more parts or remove parts.

8. When the Review Release dialog opens you can make any edits you want:
   1. Change the parts listed by deleting and adding parts, if desired
   2. Alter the Revision or Part number
   3. Alter the release name, include release notes
9. Supply the necessary approvers and observers.

10. Note that all comments from the previous release are still present (click the comment history link to access the comments for the release package):

    

11. If the release candidate required fields are complete, you can act on the Release candidate depending on your role (Apply, Release, Reject, or Discard) from the comment dialog (shown above). If any of the fields are incomplete, you must return to the Review Release dialog.

    Click the arrow icon at the bottom of the dialog, or the Comments link at the top to return to the Review Release dialog and complete the fields.

    

    

    Then you can act on the release (Apply, Release, Reject, or Discard) depending on your role.

Tips

• Clone is available while viewing a workspace in the same document as the release, and will clone the release into that workspace.
• Comments from the original releases are shown on the Comments page of the Release dialog, with links to view the original releases. You get comments all the way down the chain, so if you clone release B from release A, and release C from release B, C’s comments will show comments from both release A and release B.
• When cloning, any top-level item that can’t be found in the clone’s workspace will not be included in the cloned release.

---