-
Bug
-
Resolution: Unresolved
-
Low
-
7
-
Severity 3 - Minor
-
1
-
Summary
It is not possible to import JSON file to existing project
Steps to Reproduce
- Create a JSON file for example:
{ "projects": [ { "name": "ITF project", "key": "ITF", "issues": [ { "key" : "ITF-5555", "status" : "Open", "reporter" : "admin", "summary" : "Someting in summary" } ] } ] }
- Try to import JSON file by selecting existing project
Expected Results
Issues are created
Actual Results
Issues are not created. An example error message is shown:
External issue null already exists as ITF-1, not importing.
Workaround
- Import the file by selecting a new project
- Move the issues to the existing project.
- is related to
-
-
- Gathering Impact
-
[JRACLOUD-81934] Not possible to import JSON file to existing project
Hello!
We’re looking to improve the import experience in Jira and are keen to understand how our community is using the Jira Import Module (JIM). If you’ve used JIM to migrate/move data into Jira recently, we’d love to hear about your experience. Please take a few minutes to fill out this survey. Your feedback will help us learn how we can improve your experience in importing data.
Survey link - https://forms.gle/NYNkmS92r96z42QV9
Thanks!
Prashanth M
Product Manager, Jira Platform
Currently, this is considered a bug in Jira as there is this difference in behaviour from first imported project vs all other projects afterwards.
Workaround is to create a simple mockup project (as the first one that has "ExternalID" field) and then do imports of other projects which will then allow idempotency using "ExternalID".
Trying to do the same with an export from Zendesk to import into Service Desk and it's not working
This is happening to me, and with multiple projects. I tried a file that worked earlier and it is not working now. I can't import anything with JSON.
I can still reproduce this issue. Adding this extra UI error for searchability: