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 Submitted
Categories Source Control
Created by Guest
Created on Sep 29, 2026

Unique names for SCM Baselines

Re-opened ticket ENGEWM-I-784

Current behavior:

  • In SCM there is a trigger "Ensure Snapshot Names are Unique" that restricts the creation of Snapshots with the same name on the same stream
  • For baselines there is no option to restrict the creation of a baseline with the same name on a specific component

Desired behavior:

  • Provide the possibility to restrict also the baseline creations with the same name for one component. Example if I have a component A with a baseline "Release 1" if I try to create another baseline for component A with the same name "Release 1" I should get an error.
  • The second improvement is for the "Ensure Snapshot Names are Unique" trigger - we would like this to be configurable to the entire project Area if needed, and check the uniquity of the Snapshot name across all Streams in the same Project Area

 

Comment/question from IBM in ENGEWM-I-784:

The EWM Ideas Review board looked at this request. We understand that the request is to ensure that a snapshot name to be unique across streams, meaning if name "snapshot1" is taken for any stream, it can not be taken up for any snapshot of any stream in that repository. We would appreciate if you can confirm our understanding of the request and also share the use case and the rationale for it.

In addition, we would also like to better understand why the existing precondition is not sufficient.

Answer:

Yes, "Ensure Snapshot Names are Unique" shall respect all streams in the same project area. So, available selections shall be "No", "In the containing stream" and "In all streams in this project area". Use case is that project areas exist, which cover streams for different project and sub-projects. Creating the same snapshot name more than once creates confusion, so we would like to prevent using the same snapshot name twice in the project area.

The same behaviour is also desired for baseline creation/naming.

Idea priority Medium
Needed By Month