Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

How to clone "software requirements" from "System component" to "Software component" when both components are in the same global configuration?

Product version: IBM ELM 7.0.3 iFix018


I cannot for the life of me figure out how to move an incorrectly placed "software requirement" from a "system component" to a "software component" when both components are in the same global configuration. See details below
 

Consider the following situation:

There are two components; System and Software. The System component has some requirements in it. Two of them have been incorrectly placed in the System component and must be moved to the Software component. The artifacts have already been linked to other artifacts in the component. How can I use the "Clone from Component..." feature in DN to move the software requirements to the Software component without changing the ID and breaking the links?

Note: This example has been simplified. In the real world there are additional streams in each GC (Additional RM, QM and AM streams).

image-2025-12-9_14-40-58.png

image-2025-12-9_14-41-44.png

image-2025-12-9_14-42-15.png

image-2025-12-9_14-43-22.png

image-2025-12-9_14-43-56.png

Strategy: Just clone them.

Result: Not allowed

image-2025-12-9_14-46-5.png

image-2025-12-9_14-46-49.png

Strategy: Create a temporary component to clone the reqs to, then delete the reqs from the System component, then clone them from the temporary component to the Software component.

image-2025-12-9_14-49-22.png

image-2025-12-9_14-50-0.png

image-2025-12-9_14-50-44.png

image-2025-12-9_14-51-9.png

image-2025-12-9_14-51-31.png

image-2025-12-9_14-52-10.png

The 2 software requirements have been cloned to the Temp component with link stubs:

image-2025-12-9_14-52-35.png

image-2025-12-9_14-52-58.png

Delete the 2 software requirements from the System component:

image-2025-12-9_14-54-2.png

image-2025-12-9_14-54-26.png

image-2025-12-9_14-55-1.png

The software requirements are gone from the System component.

Now create a new cs to clone the 2 reqs from Temp

image-2025-12-10_5-9-20.png

image-2025-12-10_5-9-48.png

image-2025-12-10_5-10-21.png

image-2025-12-10_5-10-51.png

image-2025-12-10_5-11-22.png

image-2025-12-10_5-11-43.png

Result: Operation failed. Topic link yields empty IBM page:

image-2025-12-10_5-12-12.png

Problem: It seems as if GCM still thinks that the 2 reqs are in the System component, even though they have already been deleted. The 7.0.3 page Cloning requirement artifacts states: 

image-2025-12-10_5-15-52.png

Pressing that links yields a 7.2.0 version page: Fixing overlapping components (trying to switch to 7.0.3 yields a warning that no page exist):

image-2025-12-10_5-19-16.png

Strategy to solve Problem: Refresh Component Overlap Data in the System and Software and Temp components:

image-2025-12-10_5-21-33.png

image-2025-12-10_5-22-14.png

image-2025-12-10_5-23-27.png

Try to clone the artifacts from the Temp to the Software component again:

image-2025-12-10_5-25-18.png

Problem remains:

image-2025-12-10_5-25-50.png

Strategy to solve the problem: Since the problem occurs in Markus Nordstrand's personal stream, maybe if I add the configurations to a completely new GC it will work?

Old GC:

image-2025-12-10_5-27-30.png

New GC:

image-2025-12-10_5-29-2.png

image-2025-12-10_5-29-35.png

image-2025-12-10_5-30-35.png

Clone the reqs from Temp again:

image-2025-12-10_5-31-19.png

Still error from Markus Nordstrand's System Initial Development PS.

image-2025-12-10_5-31-51.png

Strategy: Remove the configurations from Markus Nordstrand's System Initial Development:

image-2025-12-10_5-33-1.png

image-2025-12-10_5-50-32.png

Test to clone from Temp to Software again: 

image-2025-12-10_5-51-24.png

image-2025-12-10_5-51-45.png

image-2025-12-10_5-51-55.png

Same error, but now for the "System New" PS

image-2025-12-10_5-52-11.png

Strategy: Create a completely new set of Global Components: System New and Software New:

image-2025-12-10_5-53-50.png

Add the corresponding configurations:

image-2025-12-10_5-55-9.png

Again, try to clone from Temp to Software:

image-2025-12-10_5-55-59.png

image-2025-12-10_5-56-35.png

image-2025-12-10_5-56-54.png

image-2025-12-10_5-57-14.png

Problem persists:

image-2025-12-10_5-57-31.png

Strategy: Check Markus Nordstrand's System New

image-2025-12-10_5-59-31.png

Remove the configurations manually:

image-2025-12-10_6-1-6.png

Try again to clone but still fails:

image-2025-12-10_6-2-11.png

Try again to Refresh Component Overlap Data:

image-2025-12-10_6-2-57.png

Try again to clone:

image-2025-12-10_6-3-33.png

Problem persists:

image-2025-12-10_6-3-49.png

CONCLUSION: I cannot for the life of me figure out how to move a software requirement from the system component to the software component when both components are in the same global configuration.


0 votes



3 answers

Permanent link

Yes, I would be so nice if this process could be a feature in the tools directly. I created an idea for this feature: https://ideas.ibm.com/ideas/ENGRMDN-I-1239

1 vote

Comments

I voted for it. 


Permanent link

Even if you create a new component "Temp" and clone the artifact temporarily to it and delete the artifact from System, you will still not be able to clone from Temp to Software! This is because System still contain references to the deleted artifacts.

Solution: Avoid performing the clone operation from a component that has a stream that have had the artifact in the same GC:

  1. Create a new component "Temp".
  2. Clone all artifacts except the ones you want to move.
  3. Remove System's stream from the GC.
  4. Add Temp's stream to the GC.
  5. Clone the artifact you wanted to move from System to Software
  6. Change the name of System to something else, i.e. System_Archived and archive it.
  7. Change the name of Temp to System.
  8. Done!

While extremely tedious, this workaround works, still I think the tool should support this use case in a much simpler way! Moving requirements should not be this hard if the ID's and links should be maintained. 

0 votes


Permanent link

I think Markus' solution is great, but there is risk. If you do this wrong, you may hose your GC and then you have to copy and not clone. I've been there. It's no fun.

0 votes

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 12,127
× 7,603
× 1,432

Question asked: Dec 10 '25, 12:40 a.m.

Question was seen: 478 times

Last updated: Jan 22, 10:21 a.m.

Confirmation Cancel Confirm