Query abt RQMExcelImporter on updation of Testcases
Accepted answer
Hi Brijraj,
if you are using Excel Importer and not setting the external for artifacts, the Excel Importer will assign a default external with excel name and worksheet name,
so if you want creating new artifacts instead of updating, there are 2 approaches for you
1. set the external using XLSArtifactID
refer to https://jazz.net/wiki/bin/view/Main/RQMExcelWordImporter
2. rename the excel file, and make sure to select the correct config name after renaming
if you are using Excel Importer and not setting the external for artifacts, the Excel Importer will assign a default external with excel name and worksheet name,
so if you want creating new artifacts instead of updating, there are 2 approaches for you
1. set the external using XLSArtifactID
refer to https://jazz.net/wiki/bin/view/Main/RQMExcelWordImporter
2. rename the excel file, and make sure to select the correct config name after renaming
Comments
1 vote
showing 5 of 6
show 1 more comments
6 other answers
Hi Brijraj, I am assuming you are talking about importing (not exporting!!) test case in RQM. If you will import same test case; it will not create duplicate test case in RQM, in stead of that, it update same test case with no change. But if you will change test case name then Importer will create new test case into RQM.
Hi Brijraj,
I completely agree with you. We are having the exact same issue with Requirements. We've just updated to v3.0.1.3 of RQM, with fixes to some other issues that we picked up on before the upgrade. Unfortunately we did not pick up on this.
I never imagined they would remove functionality just like that!
This is making the requirements side of RQM UNUSABLE for us, since we have always used the excel import to update requirements - which also sets the suspect status for Test Cases.
We are seriously considering rolling back to version 2 and if you want to be able to use RQM with the requirement import, you'll probably have no choice but to do the same. :(((
I completely agree with you. We are having the exact same issue with Requirements. We've just updated to v3.0.1.3 of RQM, with fixes to some other issues that we picked up on before the upgrade. Unfortunately we did not pick up on this.
I never imagined they would remove functionality just like that!
This is making the requirements side of RQM UNUSABLE for us, since we have always used the excel import to update requirements - which also sets the suspect status for Test Cases.
We are seriously considering rolling back to version 2 and if you want to be able to use RQM with the requirement import, you'll probably have no choice but to do the same. :(((
Hello,
Quick update for anyone else having similar issues:
v3.0.1.3 (same as the RQM we've got) of the tool can import new requirements and update those new requirements.
There is a setting on the server Advanced settings to do with Requirements, where you would have to provide a username and password of a user that has full permissions (member with all roles) to all the RRC projects.
We are now in the process of trying to get it to also update existing requirements in the same way, i.e. the ones that were migrated from v2. This is important because we have many requirements and for the projects that had recently started quite a few will be changing. Some need to change already, so my colleagues are waiting for the outcome of this before they make any updates.
I will let you know if the issue was fixed in the end -hopefully soon!
Quick update for anyone else having similar issues:
v3.0.1.3 (same as the RQM we've got) of the tool can import new requirements and update those new requirements.
There is a setting on the server Advanced settings to do with Requirements, where you would have to provide a username and password of a user that has full permissions (member with all roles) to all the RRC projects.
We are now in the process of trying to get it to also update existing requirements in the same way, i.e. the ones that were migrated from v2. This is important because we have many requirements and for the projects that had recently started quite a few will be changing. Some need to change already, so my colleagues are waiting for the outcome of this before they make any updates.
I will let you know if the issue was fixed in the end -hopefully soon!