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 Feature
Created by Guest
Created on Jul 17, 2025

DOORS Next 7.1 Change set API. Not possible to get information.

Since DNG V7.1 it is possible to access information about content of a changeset through the API. This helps dramatically, to retrieve the modifications on artifacts for further processing, but generates less load as it was needed in V7.0.3 and earlier.

Our use case it to detect changed links between requirements (added and removed) as this kind of change cannot be detected via the modified date of an requirement.


See the DNGChangesetContentsApiOverview page as reference. The following behaviour was reproduced on V7.1 iFix003 (see Attachment: VersionInfo.png)


When information is retrieved from a change set through the API, the change details within the change set can be retrieved.


The Chain of API-Calls is:

Component (see ComponentList.png)

=> Streams (see ConfigurationList.png)

=> List of Change Sets (see DeliverdChnageSets.png)

=> Change Set (see SingleChangeSet.png)

=> Changes (see Changes.png)

=> Change Details (like links)


If the changes contain a link information, it is possible to retrieve the link details (source, target, type) through API (https://ms011.fyre.ibm.com/rm/links/LI_QB2wcDf4EfCHOp7lDoggzg ) as well, as long as the link exists between the artifacts (see API_LinkAddition.png).


As soon as the link gets removed (in a later change set), the information about the link details vanishes and even the same API-Call (https://ms011.fyre.ibm.com/rm/links/LI_QB2wcDf4EfCHOp7lDoggzg ) reports the resource as gone (API_LinkAddition_afterRemoval.png).

For retrieving information from a change set, between removed or added links, the API behaves different.


When querying the change set, that holds the removal information (through the same chain as before), the changes can be retrieved from the according CS, but details (by https://ms011.fyre.ibm.com/rm/links/LI_QB2wcDf4EfCHOp7lDoggzg) about the links in the changes are reported as gone, too (see API_LinkRemoval.png)


The fact, that the link details information is available or missing, depending on the artifacts link state (and not the historical state of the artifact) does not look correct. The information stored in a change set is supposed to be the stable over time.

Idea priority Medium
Needed By Quarter