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 Dec 21, 2023

Removed artifact(Requirement) in a module should be visible in its position in grayedout mode or Strike through

Removed artifact(Requirement) in a module should be visible in its position in grayed out mode or Strike through.

We have some scenarios where user deletes lot of Requirements and after a while they want to restore again in a module , then  it is difficult for them to find and place them under the hierarchy(Chapters) from base artifacts.

We have similar function in Doors Classic and most of our users are migrated from Doors Classic and even it is a great feature to have in Doors Next from Support Point of view.

Challenge is if user removes artifacts in bulk  (~2000) artifacts and delivers the Change Set. Later they realized 1000 of them should not be deleted then it is difficult to find and position them in right chapters.

Idea priority High
Needed By Quarter