There are bugs in the JIRA import process, JIRA (4.2.1 backup instant has been used in the import as JIRA instant), with tried different zip structure to import the attachments, attachments are fail to import.
And the structure of the attachments zip file are: (i tried one method at a time)
1) attachment folder on top level, followed by ISSUE_NUMBER folders, and followed by ISSUE_NUMBER-X folder
2) ISSUE_NUMBER folder on top level, followed by ISSUE_NUMBER-X folder
the (1) has been passed thru the validation when import, and confirm import appear, but (2) failed.
Even using (1) to import all the issues, the attachments inside all the issues is not correctly linked. And click on the link of the attachment will has the JIRA 404 (on-demand) screen.
Please suggest any solution on the problems. It will be even better if the project key amendments can be included as a full solution. Thanks.
If it is just the attachments that haven't imported properly, (and everything else is imported correctly), then Support can assist you by importing the attachments into the file system for you. As an OnDemand customer you don't have access to your file system but this is something we can assist you with.
However, if other parts of the import have also failed then I woild suggest you try the import again, without the attachments this time, and see whether you are able to just import the XML data. If that works then you shoul open a support ticket and request that we import your attachments for you separately.
All the best,
Atlassian released a security advisory on 3/20/2019. The full advisory is here: https://confluence.atlassian.com/doc/confluence-security-advisory-2019-03-20-966660264.html In a nutshe...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs