Ability to Import Bitbucket Issues into JIRA in JSON

Summary

It is not possible to import Bitbucket issues via JSON importer

Steps to Reproduce

1. Export issues from Bitbucket repository using the steps outlined on this KB article
2. Try to import JSON file by selecting the JSON option in the JIRA Import Wizard - External System Import

Expected Results

Issues are created in JIRA

Workaround

At this current point in time the below workarounds are not working anymore:

1. A simple JSON to CSV converter does not work. You have to re-format the data using something like the https://bitbucket.org/Enharmonic/bitbucket-to-jira-issue-conversion tool (that is outdated and not supported).
2. Download and install a test JIRA Server (latest version) locally. Use the native BB importer to import the issues in there. Follow the steps in below KB to merge the 2 instances together (since you only have 1 Cloud instance you can skip step #1 of the KB):
   • https://confluence.atlassian.com/jirakb/how-to-merge-two-different-jira-cloud-applications-together-779160767.html

Point #2 is not working at the moment due to another open bug introduced in Jira Server 7.13: JRASERVER-69595

Therefore, what can be done while waiting for the above bug to be fixed is the following:

1. Install a staging Jira Server using the latest 7.12 release available for download (7.12.3)
2. Use external system import to import the issues from Bitbucket Cloud into Jira Server
3. Once the issue are imported, depending on your needs, you can either:
   • Export the issues to CSV and import them in Jira Cloud. See Importing data from CSV and Creating issues using the CSV importer for details.
   • Upgrade Jira to latest 7.13 version then use the Jira Cloud Migration Assistant to import the issues in Cloud (Still EAP. Only available to customers that ask for it at the moment. For details see: About the Jira Cloud Migration Assistant early access program
   • Upgrade to a more recent Jira version (or latest) and follow the steps in the KB Merge multiple instances of Jira Cloud as explained in previous workaround.