Skip to Main Content
Cloud Platform

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:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive a notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

If you encounter any issues accessing the Ideas portals, please send email describing the issue to for resolution.

For more information about IBM's Ideas program visit

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