We are changing our JIRA project from a team managed project to company based project so my question is, once all the JIRA tickets have moved over, can we also move the AIO test cases over and keep same TC numbering etc?
If you are using Bulk Change all option to move the issues between the projects, there are two ways to do this:
Option1 : If you only want to copy cases, use AIO Tests’s Import Cases -> Other Projects
- Move the issues to destination (company based) project in Jira.Â
- Enable AIO Tests in the destination project.
- Use Import Cases -> Other Projects option to copy the cases from source to destination project.
Please note that, new case keys will be generated for the copied cases.
Option 2 : We can move the AIO Tests data for you from source to destination project. This will move all AIO Tests data, not just cases.
This approach will preserve the case key sequence. But since the project key has changed, we recommend to run an re-indexing operation which will update the case key sequence.
- Move the issues to destination (company based) project in Jira.- Reach out to us post movement of issues to proceed with the migration.
We use Jira IDs to maintain traceability / links between Jira Issues and AIO Tests data.Â
The traceability will only be preserved if the Jira Issue Ids do not change when the Jira issues are moved between projects. Please note that Bulk Change all option should preserve the same Jira Issue Ids.
Hi Richard,
If you are using Bulk Change all option to move the issues between the projects, there are two ways to do this:
Option1 : If you only want to copy cases, use AIO Tests’s Import Cases -> Other Projects
- Move the issues to destination (company based) project in Jira.Â
- Enable AIO Tests in the destination project.
- Use Import Cases -> Other Projects option to copy the cases from source to destination project.
Please note that, new case keys will be generated for the copied cases.
Option 2 : We can move the AIO Tests data for you from source to destination project. This will move all AIO Tests data, not just cases.
This approach will preserve the case key sequence. But since the project key has changed, we recommend to run an re-indexing operation which will update the case key sequence.
- Move the issues to destination (company based) project in Jira. - Reach out to us post movement of issues to proceed with the migration.
We use Jira IDs to maintain traceability / links between Jira Issues and AIO Tests data.Â
The traceability will only be preserved if the Jira Issue Ids do not change when the Jira issues are moved between projects. Please note that Bulk Change all option should preserve the same Jira Issue Ids.
Can you please open a support ticket at https://aiosupport.atlassian.net/servicedesk/customer/portal/10. Provide us with your Jira URL, and the source and destination Jira project ID / Key for us to validate the AIO Tests data.
Once we check the AIO Tests data, we can recommend the best approach.
Regards,
AIO Tests Support