Skip to Main Content
IBM Sustainability Software - Ideas Portal


This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Categories Usability
Created by Guest
Created on Jan 8, 2026

Ability to move a requirement between components in the same GC

Sometimes requirements are written in the wrong component. For instance you may have a System component and a Software component and for whatever reason some engineer incorrectly wrote some of the requirements for the Software in the System component. These requirements have been linked to other artifacts in the System component and the ID has been referenced in various documents outside of DN. 

The only operation currently implemented which allows you to reuse the same ID of the requirement and maintain the links is the "Clone" operation. However cloning artifacts in components that are in the same GC is not permitted. The only valid workaround that I have found is to:

  1. Create a new component "System_New".
  2. Clone all artifacts except the ones you want to move.
  3. Remove System's stream from the GC.
  4. Add System_New's stream to the GC.
  5. Clone the artifact you wanted to move from System to Software

This is tedious and error prone.

Therefore I would like to propose that a new feature is introduced where requirements can be moved between components in the same GC without breaking the links and without changing the ID!

Idea priority High
Needed By Yesterday (Let's go already!)
  • Guest
    Jan 13, 2026
    Have you tried to use the "Fixing overlapping components" procedure described in
    https://www.ibm.com/docs/en/engineering-lifecycle-management-suite/doors-next/7.2.0?topic=components-fixing-overlapping