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 Nov 4, 2019

Allow bilingual support for action and state names

State and action names do not allow to specify English and French name to be displayed or used in ClearQuest depending on the locale of the user or some other criteria (such as user group). As such, if states and actions are defined in English only, a French user will not be able to see the French names. This is bigger issue with our French user base. Since ClearQuest state machine is the hart of the implementing the schema business process, actions and states are the key data elements viewed and manipulated by the users. In addition, ClearQuest common components allow to be displayed in French when the user locale is set to French. Custom schema elements, such as forms and dropdown values can be manipulated in hooks to display English to English users and French to French users. So, if the same capability was available for the actions and states then it would not only satisfy bilingual requirements for federal government but also make the tool more consistent across the board.

If fact, the more overall approach would allow to define all values (states, actions, dynamic lists, reference display fields etc...) with both official languages and the value for the language based either on the user locale or on the user group membership would be used.

Extension to this framework would be to allow defining multiple languages (for example English, French, Spanish)

Idea Priority High
Use Case
French user logs into the system. All common CQ elements and the form are displayed in French. The field state (if placed on the form) shows the French value. When the user expands the change state menu (Changer l'Etat) the values of actions in that menu are displayed in French. When an English user logs into the system, the English values under Change State would be displayed in this case.
RFE ID 137829
RFE Product Rational ClearQuest
  • Guest
    Dec 2, 2019

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