Unable to move the folders from Classic project to e-Signature project encountering an error.

Question

In the Test Case Manual tracker, Unable to move the folders from Classic project to e-Signature project encountering an error.

Error:

"No items were moved, because some ReqIF identifiers are already used on the default/branch tracker."
&
"java.lang.IllegalArgumentException: Attempt to update non head revision #1 of [10480398] /Comment-1696249646776(head #2)"

According to the PTC team, this is a long-standing known limitation. Unfortunately, there is no workaround, as the system is functioning as designed.
If the target tracker already has same reqif ID, then it will refuse move operation.

From the user’s perspective, moving these items to an empty location should not cause any conflicts. Additionally, the majority of other items from the same location were transferred without any issues. Therefore, it is unclear why these identifier conflicts are occurring, and the user strongly wishes to have this functionality available.

GeoffreyClemm · Answer

If there already is an item with that reqif ID in the target tracker, and Codebeamer allowed you to add a second item with that reqif ID to the target tracker, what do you expect the system to do if that tracker is exported in a ReqIF file and that ReqIF file is then imported into a repository.  What content should the item with that reqif ID have after the import?  There would be two different items with that same reqif ID in the ReqIF file.

Sign up

Please use your PTC eSupport account.

Welcome to the PTC Community

Please use your PTC eSupport account.

Scanning file for viruses.

This file cannot be downloaded