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 Feb 12, 2024

Locked requirements are not visible at personal Stream

Current Situation: Locked requirements at DNX are not visible as locked requirements if a personal stream is created and can be changed at this CS. The user is able to modify the requirements and when he wants to deliver the CS he is informed that he can not do it, as some of the changed requirements were locked.

CS delivery is not possible (OK), but it should be avoided that locked requirements are modified.

See attached pictures.

Expected situation: Locked artifacts should be visible for all users even when they are in a CS. This will avoid the situation when a user is modifying some artifacts, only to find out minutes later that he was not supposed to do those changes and that they will not be delivered any way.

Workaround suggested by IBM:  When delivering the changeset, the locked artifacts preventing delivery are listed below the error. You can simply navigate to the artifact in the local stream and remove the lock, then continue to deliver the changeset.  -> is very dangerous, it comes against the principle of using the "Lock" functionality

Idea priority Medium
Needed By Month