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 (https://ideas.ibm.com).
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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
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)
Do not place IBM confidential, company confidential, or personal information into any field.