IBM Sustainability Software - Ideas Portal
This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. 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 updates on 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
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
This TCER Query is grouped by test case and is used to identify instances where we do not have consensus between Business Units on Test disposition, or when test results from one business unit potentially invalidate the test results of an other business unit.
In this example we see that unresolved defect 94035 that is blocking one business unit from testing something. The fix to the defect may invalidate the result of "Passed" given by the other business units.
We can save the query, but the formatting is not preserved. Because we are unable to lock the formatting of query results we have to train dozens of users to build it on the fly each time they need to perform this kind of analysis. For Example: If a user A runs the query with proper formatting as shown above. When user B runs the query they see the results presented in a different format.
This makes the query inefficient or impractical for the majority of our users.
See Attachment
This TCER Query is grouped by test case and is used to identify instances where we do not have consensus between Business Units on Test disposition, or when test results from one business unit potentially invalidate the test results of an other business unit.
In this example we see that unresolved defect 94035 that is blocking one business unit from testing something. The fix to the defect may invalidate the result of "Passed" given by the other business units.
We can save the query, but the formatting is not preserved. Because we are unable to lock the formatting of query results we have to train dozens of users to build it on the fly each time they need to perform this kind of analysis. For Example: If a user A runs the query with proper formatting as shown above. When user B runs the query they see the results presented in a different format.
This makes the query inefficient or impractical for the majority of our users.
See Attachment
This TCER Query is grouped by test case and is used to identify instances where we do not have consensus between Business Units on Test disposition, or when test results from one business unit potentially invalidate the test results of an other business unit.
In this example we see that unresolved defect 94035 that is blocking one business unit from testing something. The fix to the defect may invalidate the result of "Passed" given by the other business units.
We can save the query, but the formatting is not preserved. Because we are unable to lock the formatting of query results we have to train dozens of users to build it on the fly each time they need to perform this kind of analysis. For Example: If a user A runs the query with proper formatting as shown above. When user B runs the query they see the results presented in a different format.
This makes the query inefficient or impractical for the majority of our users.
See Attachment
This is a valid request and can be considered for a future release where we are making a number of changes to the display options.