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 Oct 2, 2017

ClearQuest EXEs not signed by IBM

We're trying to work with our security teams to create policies that will allow ClearQuest to run at a higher level of permission elevation in our environments. Software on our user's machines is very tightly managed to not allow registry updates or command line calls by default.

The ClearQuest executables we've tested (using v8.0.1.13 on Windows 10):

cqdbsetup.exe (Maintenance Tool)
clearquest.exe (both the Win32 client AND the RCP Client)

do not seem to be digitally signed. The Description comes back as either blank or very rudimentary ("clearquest" or "cqdbsetup") and the Publisher comes back as blank (instead of "IBM Rational" or something more meaningful). This is making it difficult for our security teams to make policy exceptions for ClearQuest because of the ease the application could be spoofed without some of this embedded info making it more difficult for a malicious attacker.

We're requesting that in a later version of ClearQuest, IBM takes steps to "sign" their software to make it easier for enterprise business security software to trust elevating their applications.

Idea priority Low
RFE ID 111023
RFE Product Rational ClearQuest
  • Guest
    Oct 9, 2017

    A preliminary evaluation of this request indicates that it is consistent with our business strategy. Further evaluation of this RFE is underway.