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 ClearQuest
Created by Guest
Created on Jan 9, 2020

Controlling the display of CQ repositories in ClearQuest login

Currently whatever repositories

Looking for a mechanism to restrict the list of repositories displayed during login in CQWeb based on an entry in the CQ Web URL. At the moment all available repositories from the server [Maintenance Tool] are displayed in login page.

Our requirement is to
redirect users to different set of schema repositories [in CQ login page] according to their Web link to the same server [keyword in URL]

Idea priority High
RFE ID 139298
RFE Product Rational ClearQuest
  • Guest
    May 12, 2021

    Dear Development Team,

    We all together had a discussion on Apr 20, 2021 regarding the workaround we have. Also we demonstrated how we implemented it. We are waiting for your further feedback on this topic.


  • Guest
    Jun 2, 2020


    Our requirement is kind of both usability and security. For example, in our case one set of user group should see only their own repositories and not all repositories [but all repo on the same server]. So we need a mechanism to configure it in such a way the user won't see what other repositories available. The additional attribute in the URL is what we assumed as a option to perform this. But if there are any other alternate way to accomplish our requirement, we are ready to explore.

  • Guest
    Feb 10, 2020


    We like this RFE. We want to confirm what aspect your focus is on. The convenience of usability or the security of the product?
    When the user accesses CQWeb with the default URL, what repositories should be displayed? Or is this not an allowed URL in your use cases?

    CQ Dev