We are trying to json export issues from main jira instance and to import in a secondary jira install.
It works very well in many aspects I think it is still best than project import, but it has a weakness, an inexplicable and incomprehensible weakness, It is no possible to import attachments. (at least we couldn't)
What we cant understand is that your exported json file from system A is perfectly understandable by system B (both jira servers, same versions, etc) but you can't carry attachments.
We tried many ways, copying the attachment to the folder in the same place were it will be in destination system but it is ignored when you import Json issue.
We cant understand why it is ignored if the attachment file has the same name (numeric name) that is specified in Json.
Also we tried putting attachments in Attachment folder into import folder, also ignored.
The json file (attachment section looks like) so we recreate the same folder system but it is ignored. we cant understand why.
After that we saw a documentation: https://support.atlassian.com/jira-cloud-administration/docs/import-data-from-json/
There it explains a way to form your json code to import attachments but we have to reformulate the whole attachment section, it is a lot of effort if you want to import hundreds of issues.
So again, we cannot understand why the json code generated in the origin is not valid to handle the attachment import task and you have to refurbish to the right side code style.
So, the million dollar question, Has anyone been able to do Json attachment import without having to reformulate code?
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events