Xray Migration Tool - Test Step Import handler is looking up for issue objects in Jira-Target using the issuekey

Note: Jira-Origin is where the backup file is generated, Jira-Target is where the project is imported

The Xray Migration Tool looks up for issues in Jira-Target using issuekeys on the backup file without validating its issuetype nor its content, to build ID mappings (for instance step old id to step new id), for associating Xray entities (for instance to associate Tests to Test Plans), assuming that the issue in Jira-Origin is the same in the Jira-Target.

This fails under some cases:

Test Step Import: Mapping the step old id to the new id

• step old id = id of the step in Jira-Origin
• step new id = id of the step in Jira-Target

Let's imagine that the admin generates a backup file, in the Jira-Origin. Let's call this backup file BCK1.

Then some time passes by, let's say a week. During that time a user creates the issue A-2 in the project A, in the Jira-Origin, with the following steps:

The admin then imports the project A in the Jira-Target, using the backup file BCK1. The project A is imported with success - Note that the issue A-2 will not be imported since the backup file BCK1 was generated before the creation of the issue A-2 in the Jira-Origin.

Later on, the user creates an issue with issue key A-2 in the Jira-Target, with the following steps:

At this point we have two issues with same issue key in Jira-Origin and Jira-Target (issuekey = A-2), with same issuetype but with different steps.

The admin then generates a new backup file of the Jira-Origin. Let's call this backup file BCK2. This file will now have the information of the issue A-2 of the Jira-Origin.

The admin then tries to import the project B in the Jira-Target, using the backup file BCK2.

The Test Step Import phase will fail when mapping the step new id to step old id because it assumes the issue A-2 in Jira-Origin has the same steps as the issue A-2 in Jira-Target. But these issues are different.