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 Aug 20, 2024

RM-DNG Change Set Merge Needs to be at the Attribute Level

The current Doors
Next configuration management Change Set merge process occurs at the Artifact
level such that two Change Sets which modify the same Artifact but different
Attributes will show a conflict that has to be manually addressed.  This request is to have the merge process to
occur at the Attribute level such that when two change sets include changes to
the same artifact, the merge will only be in conflict if the Change Sets
include changes to the same Attribute (excluding modified by, and modified
date).
 

Given an Artifact
with three attributes Animal, Vegetable, and Mineral.
Original Artifact
has the values as follows: Animal = dog, Vegetable = carrot, Mineral = gold
Change Set A has the
values: Animal = dog, Vegetable = radish, Mineral = gold
Change Set B has the
values: Animal = dog, Vegetable = carrot, Mineral = silver
The delivery of A
and B should show no conflict and the resultant artifact after both deliveries
would have attributes: Animal = dog, Vegetable = radish, Mineral = silver.
 

One of the major
benefits of this type of merge is that automation which modifies Attributes not
edited by users will automatically merge thousands of Artifacts without manual
intervention.

Idea priority High
Needed By Yesterday (Let's go already!)