Section name will be become odd when using REST API to put
This issue is prone to be reproduced in the scenario like this:
Use REST API to get an artifact and marshal it to a file. Unmarshal that file and put it back to another project area.
After the above operations, several section names in test plan and test case become odd like
com.ibm.rqm.planning.editor.section.plan- TestObjectives
com.ibm.rqm.planning.editor.section.plan- TestScope
com.ibm.rqm.planning- .editor.section.test- CasePreCondition
Use REST API to get an artifact and marshal it to a file. Unmarshal that file and put it back to another project area.
After the above operations, several section names in test plan and test case become odd like
com.ibm.rqm.planning.editor.section.plan- TestObjectives
com.ibm.rqm.planning.editor.section.plan- TestScope
com.ibm.rqm.planning- .editor.section.test- CasePreCondition
One answer
Can you provide your XML files?
Are the project area process templates different? Is the test plan/case template different between project areas?
I tested the same scenario and it worked fine in RQM 3.5 M1.
On a PUT/POST request, if a resource property is not recognized, a custom section is created.
Are the project area process templates different? Is the test plan/case template different between project areas?
I tested the same scenario and it worked fine in RQM 3.5 M1.
On a PUT/POST request, if a resource property is not recognized, a custom section is created.