FogBugz importer using wrong URL for downloading attachments

Question

I'm using the FogBugz OnDemand importer to import into JIRA, from a hosted FogBugz instance.

It's working well for all the cases, but I found that it's not able to download any attachments from FogBugz.

For the API, it's using the vroot /FogBugz:

2014-05-22 20:32:46 W3SVC1 P86494 72.51.46.8 GET /FogBugz/api.asp cmd=listProjects&token=vcm0d92fujvfarg66dge3ai7vosl88 80 - 72.52.75.204 HTTP/1.1 Apache-HttpClient/4.2.5+(java+1.5) - - xxx.com200 0 0 1770 186 51

But when it tries to grab the attachments, it's using the root page (default.asp), not /FogBugz/default.asp.2014-05-22 20:32:29 W3SVC1 P86494 72.51.46.8 GET /default.asp pg=pgDownload&pgType=pgFile&ixBugEvent=21537&ixAttachment=372&sFileName=STL-tech3264.pdf&sTicket=&token=vcm0d92fujvfarg66dge3ai7vosl88 80 - 72.52.75.204 HTTP/1.1 Apache-HttpClient/4.2.5+(java+1.5) - - xxx.com404 0 2 1405 263 10

Could this be a bug in the importer, or is it getting that root page from the FogBugz configuration somehow?

Thanks,
Kirk

pborkowski · Accepted Answer

Hi Kirk,

I checked this in our testing environment and... you are right... Our Importer is not respecting the whole BaseURL path of your FogBugz server while downloading attachments. I've created an issue for that: https://ecosystem.atlassian.net/browse/JIM-1301and put it to my current Sprint. It should be fixed within next ~2 weeks and put in Marketplace (so it will be available for JIRA BTF customers), but our OnDemand environment requires additonal QA period, so this fix will be there in about ~4 weeks.

If this date is not acceptable for you, please let me know - I will share with you an RC version of the importer as soon as this bug is fixed.

Cheers,

Przemek