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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
We've seen issues with other customers, where the values for Test Script Status do not align with those for the Test Case. The error message "The test script state is not synchronsized with the test case state" is an indicator of this. Please open a support case for this to confirm the configuration and alignment between states of the Test artifacts to confirm this is not a configuration issue. If it's not found to be a configuration issue, then we would consider this a defect.
https://www.ibm.com/mysupport/s/?language=en_US
Hi, this does not concern the Test execution but the Writing Status.
Then the workflow is related to the Writing Status for Test Case and Test Script.
Best regards,
Maxime
This issue is noticed when a custom workflow is configured for Test Case and Test Script.