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 Integrations
Created by Guest
Created on Nov 21, 2023

DOORS Next Change Set REST API needed

Need to report on the history of the requirements.
The DOORS Next API allows to see all the details with the history=true parameter.

The issue is that this history can grow exponentially and be very time consuming to parse.
Also we want to filter based on some change set, or base on when those CS were delivered (not created).

It would be more efficient for the user/report to start with a list of Change Set (CS) and have the history from those CS.

Using a REST Client we can have some information about the CS (I assume that is not a public API)
i.e. https://<server>/rm/cm/changeset/<UUID>

Like
    <dcterms:created
    <dcterms:title
    <dcterms:creator

But more is required, such as the history changeLog render by history=true

<history:changeLog>
        <rrm:creator>
        <rrm:modified>
        <history:changeOrigin history:changeEvent="ARTIFACT">
            <rrm:about>
            <rrm:title>
        </history:changeOrigin>
        <history:changeEntry history:changeEvent="ATTRIBUTE" history:eventType="ADDED">
            <rrm:title>Primary Text</rrm:title>
            <history:value type="url">
        </history:changeEntry>
        <history:changeEntry history:changeEvent="ATTRIBUTE" history:eventType="MODIFIED">
            <rrm:title>Title</rrm:title>
            <history:value type="string">
        </history:changeEntry>
</history:changeLog>

A CS can be created in a Stream and deliver to another Stream.
Currently there seem to be no way (including the UI) to know when the CS was deliver to the Stream.

Currently we know when the CS was created, but not delivered.
Therefore a history of the CS is necessary
      Created By
      Created On
      Created In  (Context Stream)
     
      Delivery History (0..*)
              Deliver Against (Steam
              Deliver When

 

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