Skip to Main Content
Cloud Platform


This is an IBM Automation portal for Cloud Platform products. 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
Workspace Heritage
Categories ClearCase
Created by Guest
Created on Aug 13, 2025

Modify CMI association to add ONE changeset item at a time instead of sending the whole changeset every time.

The default CMI integration behavior when adding a new task association appears to be:

  1. Download the defect/task's entire changeset
  2. Validate that changeset
  3. Add/append the new items to the changeset.
  4. Post the ENTIRE modified list to the CMI provider. 

Downloading and validating the changeset seems a little extreme, but is probably an acceptable sanity check to avoid double associations. However, posting the entire modified changeset back to the CMI provider seems excessive. Just posting the deltas (add this/these, remove this/these) is significantly more efficient. 

This impacts both migration and normal use of the product when performing CMI task associations.

  • Admin
    Muriel Viale
    Sep 10, 2025

    A preliminary evaluation of this request indicates that it is consistent

    with our business strategy. Further evaluation of this RFE is underway.