“Copy from Component” Does Not Recognize Components on Different RM Servers Despite Shared Global Configuration

In IBM DOORS Next 7.1, the “Copy from Component” operation does not display components that reside on different RM servers, even when all components are correctly included in the same Global Configuration (GC).

According to expected behavior, a GC should define the scope of visible components for cross‑component operations is determined by the Global Configuration. However, DNG is only showing components hosted on the local server from which the operation is initiated.

Problem Behavior

When a GC contains components from multiple DNG servers (e.g., RM1, RM2, RM3), and a user opens a component on one of them (e.g., RM3) and attempts to perform Copy from Component, (or search across components)  the selection list only displays components from RM3. All components from RM1 and RM2 are missing.

For example the Global Configuration AGC contains the following components distributed across 3 servers: 

• RM1: 50 components
• RM2: 30 components
• RM3: 20 components

If the user is working in a component on RM3, the Copy from Component list shows only 19 other components instead of the expected 99  (the current component is not counted here).

Impact

• Cross‑server reuse becomes impossible, even though the GC includes all relevant components.
• Usability of DNG in the ELM multi‑server environment is severely constrained.
• This contradicts IBM’s recent fix that restored server‑to‑server linking; linking now works, but copying does not recognize remote components.

Request

Please investigate and resolve the defect preventing Copy from Component (and related search operations) from recognizing components on other RM servers, even when they are part of the same Global Configuration.

This issue significantly affects our ability to reuse requirements across servers and is a critical blocker for our teams.