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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Categories ClearCase
Created by Guest
Created on Dec 12, 2023

Keep ClearCase/ClearQuest V2 Integration in future releases. It is already implemented and changing to the CMI integration has negative impacts.

Keep ClearCase/ClearQuest V2 Integration in future releases.  It is already implemented and changing to the CMI integration has negative impacts.

CC/CQ V2 Integration was announced as deprecated in 9.1/10.x, yet still functions.  Functionality will be disabled in future versions, starting in 2024.  Directions are to migrate to CC/CQ CMI Integration.

Keep CC/CQ V2 Integration.  It is currently implemented and functional.  Continued support in future releases should be minimal, only requiring regression testing and updates if underlying dependencies change, such as Perl version changes.

Sites that currently use CC/CQ V2 Integration should be able to continue using it with little to no impacts.

Migrating to CC/CQ CMI Integration has several negative impacts to a site:

- Requires CQ Web services.  Some site cannot implement CQ Web.  E.g. company policies, closed secure labs, etc.

- Requires a CQ OSLC package be applied to all schemas and deployed to the databases.  Some sites cannot update their schemas for various reasons.  

- Requires CC VOBs have attribute objects and CMI providers created.  

- The effort to perform these changes may seem insignificant for a single CC/CQ pair.  An update may actually involve having to get program approval, security approval, update CC VOBs and CQ databases, test, and deploy.  This effort scales up when multiple VOBs or databases are involved.  Some site may have dozens or hundreds of repositories.

The CC/CQ Integration Configuration App may be used to select V1 (deprecated and disabled), V2 (depreciate but functional) to specify the VOB, VOB details (branches, etc), and CQ record type.  For the new 10.x releases, this includes a new tab to specify a CQ schema and have the app add the required CQ OSLC package and CC objects for CMI integration.

The new functionality that I was hoping to see in the CC/CQ Integration Configuration App was to offer a tab to select or enter fields for the V2 perl file details and update that file rather than require the admin edit the raw source file. 

Idea priority Medium