Issues importing from FogBugz

Trying to import from FB 7.6.3 server instance to a Jira on demand.

FB is externally accessible and I can connect fine - it imports users but fails when importing issues. I removed all field mappings except the mandatory 3 and it still fails.

Log shows the error:

2013-06-05 12:02:30,084 INFO - Only new items will be

imported
2013-06-05 12:03:05,812 INFO -

------------------------------
2013-06-05 12:03:05,813 INFO - Finished Importing :

Issues
2013-06-05 12:03:05,813 INFO -

------------------------------
2013-06-05 12:03:05,813 ERROR - Unexpected failure

occurred. Importer will stop immediately. Data maybe

in an unstable state
org.jdom.IllegalDataException: The data "Ther is

nothing usefull in logs even in txt file, the only

error is:

<absfile><![CDATA[Error.FailedChannelRequest]]

></absfile>" is not legal for a JDOM CDATA section:

CDATA cannot internally contain a CDATA ending

delimiter (]]>).
at org.jdom.CDATA.setText(CDATA.java:121)
at org.jdom.CDATA.<init>(CDATA.java:95)
at org.jdom.DefaultJDOMFactory.cdata

(DefaultJDOMFactory.java:97)
at org.jdom.input.SAXHandler.flushCharacters

(SAXHandler.java:652)
at org.jdom.input.SAXHandler.flushCharacters

(SAXHandler.java:623)
at org.jdom.input.SAXHandler.endElement

(SAXHandler.java:678)
at

org.apache.xerces.parsers.AbstractSAXParser.endElement

(Unknown Source)
at

org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEn

dElement(Unknown Source)
at

org.apache.xerces.impl.XMLDocumentFragmentScannerImpl

$FragmentContentDispatcher.dispatch(Unknown Source)
at

org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.

scanDocument(Unknown Source)
at

org.apache.xerces.parsers.XML11Configuration.parse

(Unknown Source)
at

org.apache.xerces.parsers.XML11Configuration.parse

(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse

(Unknown Source)
at

org.apache.xerces.parsers.AbstractSAXParser.parse

(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl

$JAXPSAXParser.parse(Unknown Source)
at org.jdom.input.SAXBuilder.build

(SAXBuilder.java:453)
at org.jdom.input.SAXBuilder.build

(SAXBuilder.java:770)
at

com.atlassian.jira.plugins.importer.imports.fogbugz.ho

sted.FogBugzClient.getWithToken

(FogBugzClient.java:223)
at

com.atlassian.jira.plugins.importer.imports.fogbugz.ho

sted.FogBugzClient.getCases(FogBugzClient.java:275)
at

com.atlassian.jira.plugins.importer.imports.fogbugz.ho

sted.FogBugzHostedDataBean.getIssuesIterator

(FogBugzHostedDataBean.java:132)
at

com.atlassian.jira.plugins.importer.imports.importer.i

mpl.DefaultJiraDataImporter.importIssues

(DefaultJiraDataImporter.java:809)
at

com.atlassian.jira.plugins.importer.imports.importer.i

mpl.DefaultJiraDataImporter.doImport

(DefaultJiraDataImporter.java:415)
at

com.atlassian.jira.plugins.importer.imports.importer.i

mpl.ImporterCallable.call(ImporterCallable.java:26)
at

com.atlassian.jira.plugins.importer.imports.importer.i

mpl.ImporterCallable.call(ImporterCallable.java:15)
at com.atlassian.jira.task.TaskManagerImpl

$TaskCallableDecorator.call(TaskManagerImpl.java:365)
at java.util.concurrent.FutureTask

$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run

(FutureTask.java:138)
at java.util.concurrent.Executors

$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask

$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run

(FutureTask.java:138)
at

com.atlassian.jira.task.ForkedThreadExecutor

$ForkedRunnableDecorator.run

(ForkedThreadExecutor.java:249)
at java.lang.Thread.run(Thread.java:662)
2013-06-05 12:03:06,391 INFO - No issues need to be

reindexed.

2 answers

This widget could not be displayed.

I ran into the same issue and was able to solve it by simply searching in fogbugz for the keyword "CDATA" and then editing this word out of all cases. As soon as I cleared this out of our fogbugz cases, the import went smoothly.

Thanks for the workaround Paul, I figured that would solve this (which I have also run into). However, JIRA should really address this... my FogBugz data is perfectly valid, it's JIRA's importer that's falling down :)

This widget could not be displayed.

I was able to import from a different project within the same FB install

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted yesterday in New to Jira

Are you planning to trial, or are currently trialling Jira Software? - We want to talk to you!

Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in   talking to 20 people planning t...

82 views 1 0
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you