Structure Import

Overview

T4J provides a way to export a test plan structure from one project and import it as new folders and issues in another project.

This feature is currently only available to administrators.

Exporting a test plan

Follow the instructions to export a test plan in JSON format in Test Plans - How-to Guide.

Any user can export a test plan, but import is only allowed to administrators.

Importing a test plan

  • Modify the file that has been previously exported, as described in the section How to modify an exported plan file for import.

  • Select the Plan entry in the main T4J menu.

  • Select the Import dropdown menu entry in the set of R4J menus.

  • Select the file in the dialog Import Test Plan.

  • Select Browse to open the file explorer and choose a previously exported JSON file.

  • Select Import.

The results of a successful import are the following:

  • A new test plan exists in the destination project.

  • The issues in the test plan have been duplicated in the destination project. (Issues that already existed in the destination project are not duplicated. This can occur if the test plan in the source project used issues in the destination project by reference.)

  • The project tree contains a new folder and subfolders corresponding to the test plan folder and its subfolders.

Errors in file content structure or data result in the failure of the import.

How to modify an exported test plan file for import

The plan export produces a file that sets the following attributes to values for the plan that is being exported:

  • prjKey: the key of the plan’s project

  • name: the name of the plan

The project key must be changed to the key of the destination project. If that project already contains a plan with the same name, the name must also be changed.

Limitations of Import

  • Import is restricted to projects that have the same issue type scheme as that of the source project.

  • Only issue links between issues in the same test plan are imported.

  • Attachments are not imported.

  • The values of Versions and Components fields are not imported.

Â