Having issue with our Importer utility for Zephyr for Jira Cloud.Please click here for the steps to resolve the issue. If you are not able to access Capture Cloud and seeing a message, it means your Capture cloud instance is not migrated as part of our GDPR and Atlassian privacy policy. Please click here for the steps to Migrate your Capture Cloud instance to use Capture.
Support | Zephyr



Zephyr Importer Tips

Created on

The Zephyr Importer is a powerful tool that can help your team import test cases and other Standard JIRA Issue types to both ZFJ Server and ZFJ Cloud from exported files or even made-from-scratch files. In fact, ZFJ Server now has an internal importer natively. We'd recommend reading through these two articles before hand:

 - How Do I Import Test Cases Into Zephyr For JIRA Server/Cloud? -

 - Getting started with the Zephyr for JIRA Importer Utility -

 

Here are some additional tips to help you properly import your test cases:

1) Each row should represent a single step of each test case. It may take multiple rows to properly represent a single test case.


2) Ensure your discriminator choice parallels how your data is formatted in your import file. Make sure your discriminator never meets an empty cell. It's good practice to keep null and empty cells out of the spreadsheet whenever possible.


3) If you can see the field from the project's “Create issue” prompt, you can see the field in the importer.


4) Use Java 8 if using the JAR importer.


5) Non plaintext Custom fields, such as checkboxes and radios,  are unsupported/experimental.


6) Fields with prepopulated values, like Version and Components, must have values preexisting in JIRA prior to importation.


7) Name should be what you’d expect to see as the Summary in JIRA , and External ID is the unique value that represents each test case.


8) For appending test case steps, simply leave the External ID field unmapped and instead map the Issue Key field. Ensure that the entries for Issue Key in your import file match JIRA's issue keys.

 

9) Before you hit import, make sure to save the last field mapped by selecting a different cell. This may sound trivial, but the importer may fail to save your last entered field since it thinks you are still editing it.


Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request
Powered by Zendesk