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 Under review
Categories Usability
Created by Guest
Created on Mar 26, 2024

Hard to audit changeset after delivery

Difficult to audit a changeset after delivery.
Harder after delivery when trying to go back to see what changed. How to diff?
No compare with stream option. Instead need to piece meal the changes together. Piece together starting and ending state of the requirement. Have to look at timestamps, but not perfect. ...or requirement may be deleted and can't find it anymore because it is gone now.
Using baselines solves this but causes DB growth.

No compare with Stream. Need diff on modules. But, have to look at every artifact for each module. Need individual change history on "each line" vs each module. Could do baseline, but that grows the database. Also have deliveries to different customers, so overlapping.  It is in the history of the artifact, but no convienient way to see. Not just for customer audits, but also used in day to day. For example, looking at a bug and trying to figure out when it was introduced and it is not easy. Cumbersome. History loses context of change set. If have overlapping changesets, which doesn't happen often, but does happen in parallel development. If two changesets change the same artifact in the same lifecycle and then deliver both. In the audit, it doesn't have the history separated by changeset so can't just go by date/time. Need before vs after the story was worked. 

Idea priority High
Needed By Yesterday (Let's go already!)
  • Guest
    Reply
    |
    Apr 19, 2024
    From the "Manage Components and Configurations" , it is possible to browse the components.
    Then, from that Browse components view, it is possible to open any existing streams for that component.
    While looking at a specific stream of a component in that view, it is possible to select the "Change Sets" tab and then the option to "Include delivered change sets" on the right hand side of the tool bar.
    Now, you can see and select one of the delivered change sets to that stream and the Changed Resources included in that change set.
    Please let me know what else would be required to audit change set after delivery.