-
Bug
-
Resolution: Fixed
-
Medium (View bug fix roadmap)
-
3.13, 3.13.1
-
Standalone, MySQL
-
3.13
-
Whenever you try to import a project without attachments the process fails. Error reads:
There was a problem parsing the backup XML file at /Users/jcostello/jiraeditions/atlassian-jira-enterprise-3.13-standalone/customerdata.zip: A file attachment with id '11978' must have a file name specified.
Steps to reproduce;
1. Import a Project from xml or zip
2. Do not define attachments
3. Follow the import process. On the third screen the error message will appear.
KNOWN FIX
Go into the xml backup, find the line with the error by id:
Example broken line: Notice filename=""
<FileAttachment id="11978" issue="15356" mimetype="application/octet-stream" filename="" created="2005-01-31 11:32:17.0" filesize="33280" author="cvp"/>
Example Fix: change the filename="somefile.bin" or to whatever you would like it to be named.
<FileAttachment id="11978" issue="15356" mimetype="application/octet-stream" filename="somefile.bin" created="2005-01-31 11:32:17.0" filesize="33280" author="cvp"/>
JIRA will then allow the import process to proceed.
[JRASERVER-15914] Project import failing without attachments.
Made the project import able to proceed if the XML file contains empty filename values for FileAttachments.
The user will get a warning on screen.
Andy Brook (Javahollic Software)
added a comment - It would be nice to extend the Jira sanity checking to assert such judgment calls before the XML backup is generated. I just love the 1) check my system 2) now go fix it approach. Stripping out files that have no name or don't exist would certainly be useful.
Andy Brook (Javahollic Software)
added a comment - It would be nice to extend the Jira sanity checking to assert such judgment calls before the XML backup is generated. I just love the 1) check my system 2) now go fix it approach. Stripping out files that have no name or don't exist would certainly be useful. Thanks fore reporting this problem. I spoke to the lead developer on this component and he explained the rational behind this check.
Basically they tried to find a balance between ensuring data makes sense and letting inconsistent but useable data come through.
Obviously in this case we are being too strict. That said a imported file without a name is not very useful either.
Thanks also for documenting the work around
Verified with QA bamboo build 235 on IE7.0. The issue is resolved