AIO Tests allows you to import cases from other AIO Tests projects with the click of a button. By importing cases, you can copy test cases belonging to another Jira project in which AIO Tests are enabled to any other project where AIO Tests are enabled.
In this documentation, you’ll understand:
Overview of the Process
Steps to Import Cases from Other AIO Tests Projects
Step 1: To import cases from other projects, select the destination project where you want to import the cases.
Step 2: Click on the Cases option in the top bar menu.
Step 3: Click on the Import Cases button.
Step 4: On the import cases page, you will get 3 tabs on the Import Cases view- File, Other Projects, and Jobs. Click on the Other Projects tab.
Step 5: On the Projects section, select the source project from the Project Selector drop-down menu.
By default, the current project’s cases are loaded.
Step 6: Once you select the source project, select the cases that you want to import.
Users also have the option to search and select the cases to be copied using search/filter.
Step 7: Click on the Select Configuration button.
Step 8: On the Select Configuration section, specify the import preferences and choose the target folder in which you want to copy the cases. Click on the Select Target Folder field and select the target folder from the drop-down list.
By default, the Not Assigned folder is selected but the user can select from the already created folders via the drop-down.
Users also have 3 options on the Select Configuration screen- Preserve the Folder Hierarchy?, Deep Copy linked test cases?, and Add suffix to copied cases?
Preserve the Folder Hierarchy?
If the Preserve the Folder Hierarchy option is selected, the folder structure of the cases to be copied will be re-created in the destination project under the folder selected in the target folder.
If the Preserve the Folder Hierarchy option is selected and if no target folder is specified, the folder structure of the source cases will be created at the root level in the destination project. In this case, if any source case doesn’t belong to a folder, it will be copied to the Not Assigned folder in the destination project.
If the Preserve the Folder Hierarchy option is not selected, cases will be copied to the specified target folder of the destination project.
If the Preserve the Folder Hierarchy option is not selected and if no target folder is specified, cases will be copied to the Not Assigned folder of the destination project.
Deep Copy linked test cases?
If the Deep Copy linked test cases option is selected, any linked cases in the source cases that belong to the source project will also be copied to the destination project and the new case from the destination project will be linked to the copied case.
If the Deep Copy linked test cases option is selected, any linked cases in the source cases that belong to other projects will be copied as links to the cases of other projects.
If the Deep Copy linked test cases option is not selected, copied cases will have a link to the cases belonging to the source project as well as any other project and linked cases won’t be created as a separate case in the destination project.
Add suffix to copied cases?
If the Add suffix to copied cases option is selected, “Copy” will be added at the end of the title of the copied cases.
If the Add suffix to copied cases option is not selected, the title of the copied cases will be the same as the source cases.
Step 9: Click on the Select Field Mapping button.
Users have the option to go back and update the cases list to be copied by clicking on the Select Cases button.
Step 10: If the source project has custom fields, users will be prompted to map them to existing custom fields in the destination project. Once done, users will also get an option to map the data values to values present in the destination project by clicking on the Select Data Mapping button.
If the destination project has multiple types of custom fields, and the source doesn’t, users can map the source field to only one destination field and vice-versa.
If field names are the same between the two projects, they will be mapped automatically.
If the fields are not mapped, those fields will not be copied.
If there are no custom fields in the source project, the user will directly see the Data Mapping section.
Step 11: Once you click on the Select Data Mapping button, the data mapping screen will be displayed. On the data mapping screen, users will be prompted to map values of the following fields- Priority, Status, Type, Components, Release, Automation Status and all eligible custom fields. Once done, click on the Start Import button to start the copy process.
Once you click on the Start Import button, you will be redirected to the Jobs section and a success message will be displayed on the screen stating “Batch <batch #> created successfully”.
Jobs: The Job tab shows all the import requests that have either been submitted or completed. Upon clicking the down-carat icon next to the Created Date, the result of the batch processing will be displayed on the screen, whether the import actually succeeded or not.
For further queries and suggestions, feel free to reach out to our customer support service via help@aiotests.com.