2.7.3.8.2. Move tree nodes and reassign them

Purpose

You can move a node, along with all its child nodes, to a more appropriate location within the same clustering hierarchy. This process can be initiated via the node menu or by dragging a node to a suitable destination in the tree.

Requirements

  • Log in using clustering-view and clustering-edit.

  • Open a closed cluster with a movable node (not the root) and another suitable parent node.

  • When dragging and dropping, make sure that the source and destination are visible in the cluster tree.

Procedure

Use "Move" [1] in a node's action menu if you want to manually select the destination. The dialog displays a tree of suitable parent nodes; a final confirmation screen lists the source and destination. The moved node retains its child nodes.

The context menu provides a quick way to move a node.

The context menu provides a quick way to move a node.

Select an internal node or an empty leaf outside the source branch [1] from the list. The confirmation dialog [2] lists the structural change before it is executed. Filled leaves do not appear in the destination list, since they cannot contain child nodes.

Selecting a target and confirming it clearly distinguish reassignment from other cluster operations.

Selecting a target and confirming it clearly distinguish reassignment from other cluster operations.

To work directly on the structure, drag a node (not the root) onto a suitable destination in the cluster tree. The feedback at the destination indicates a valid destination for the reassignment. The updated tree shows the node with its entire branch under the new parent node.

After reloading the saved hierarchy, the moved branch is located entirely under its new parent node.

After reloading the saved hierarchy, the moved branch is located entirely under its new parent node.

After each move, check the metrics in all affected areas: the progress circle in the tree and its tooltip for the source and destination branches, the status bars of the affected cluster maps, and the totals under “Overview.” The branch-specific values must follow the moved subtree; the total number of items and the totals for “Open,” “To check,” and “Done” remain unchanged.

Options and Decisions in Operations

Moving Nodes – Entry Points, Destinations, and Control

Control element or State

Operating Instructions

"Move"

Opens the selection of the new parent node for the selected node (not the root). Use this action when the source and destination need to be carefully checked before changing the hierarchy.

Selecting the parent node

Lists only targets that can contain child nodes. Select the new parent node for the entire source branch.

Confirmation of the rescheduling

Specify the source and destination. Confirm only if the resulting hierarchy reflects the intended structure.

Drag and Drop

Alternative direct method for the same reassignment. Drag the node row or the header of an appropriate cluster map onto a target in the tree.

Valid destination

Another internal node or an empty leaf outside the source subtree that is not the current parent node.

Invalid destination

The source itself, its current parent node, each of its child nodes, and each filled leaf cannot contain the moved branch.

Goal: to merge

If a sheet is placed on top of a filled sheet, instead of reassigning it, the system begins merging sheet clusters. This describes the merging process.

"Cancel"

Closes the destination selection or confirms without changing the saved hierarchy .

Key Figures

After a move, compare the progress circle in the tree (including the tooltip), the status bars of the affected cluster cards, and the “Overview.” The values for the source and destination branches must reflect the new hierarchy; the total counts of the parts and the check statuses remain unchanged.

Result

After reloading, the selected node and all its child nodes will appear under the confirmed new parent node. The part relationships in each moved leaf node remain unchanged.

Tips and Troubleshooting

  • After an action error, continue working only with the updated server view that the workspace displays.

  • Use the menu path if the source and destination are not both visible, or if the hierarchy change requires explicit confirmation.