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.
See this idea on ideas.ibm.com
Problem Statement: Ability to merge Test scripts from within Test case in RQM
Teams Affected: All Teams in Onshore Project area Application version: 6.0.6.1 ifix019
Priority: High
Problem: While merging, the test case changes and test script changes needs to merged separately, even if the test scripts are part of the same test case.
Description: One of our team is using a two-stream strategy, 'Initial stream' and 'development stream'. Development stream is used to create/edit/update test cases. These test cases in the development stream will be later merged to the initial stream and the test cases will be executed in the initial stream.
During the merge operation the test case changes and test script changes needs to merged separately, even if the test script scripts are part of the same test case.
We need to have the test script changes as a part of test case and merge it from the test case manually instead of having to merge it separately.
Idea priority | High |
Needed By | Month |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Changing the way we do configuration management merge would be a significant architectural change, that we are not considering. Today requires that each artifact be compared and confirmed separately.
There is a workaround to your process if you expose and use the Edit Test Script Inline section of the Test Case. This would allow you to create and update your test scripts within the Test Case, vs. as associated with the Test Case. When you perform the Merge, only Test Case will appear as an artifact for merge, and the changes made to the inline test script can be merged.
See https://www.ibm.com/docs/en/elm/7.0.3?topic=scripts-editing-manual-test for information on edit of test scripts from the test case by using the Edit Test Scripts Inline section.