Reuse and Sync Recreates the Original Project Hierarchy in the Destination Project

Summary

When using Reuse and Sync in Jama Connect, selecting Reuse source project hierarchy in destination project may recreate the original parent hierarchy of the selected item in the destination project.

This can appear unexpected when users intend to reuse only a specific child item and its descendants, without recreating the original parent folder structure.

Based on testing in Jama Connect 9.35.x, this is expected application behavior rather than a defect.

The two location options behave differently:

• Reuse source project hierarchy in destination project: Recreates the source hierarchy leading to the selected item, preserving its original location within the tree. This allows a child item to retain its original parent structure without necessarily reusing its siblings.
• Manually select location(s) for reused item(s): Allows users to choose where the selected item and its children should be placed in the destination project, without recreating the original parent hierarchy.

For example, reusing the 'Items' set with Reuse source project hierarchy in destination project selected recreates the source hierarchy in the destination project.

It is also possible to reuse a child item – for example, 'sub 2' below – while preserving its original parent hierarchy without reusing its sibling (sibling item: 'hopefully don't include me').

Resolution

To reuse only the selected item and its children without recreating the original parent hierarchy, use Manually select location(s) for reused item(s).

1. Initiate Reuse and Sync for the item you want to reuse.
2. Select Manually select location(s) for reused item(s) instead of Reuse source project hierarchy in destination project.
3. Choose the desired location in the destination project.
4. Complete the reuse operation.

For example, when reusing sub 2, manually selecting the destination project's root allows the item and its children to be placed directly under that location.

The resulting destination hierarchy contains the selected item and its children without recreating the original parent hierarchy.

This approach is recommended when users want to control where reused items are placed rather than preserve their original source hierarchy.

If the existing behavior does not meet the customer's requirements, consider submitting a feature request with a detailed description of the expected behavior for the different reuse scenarios.