Fogbugz import tool for JIRA Cloud instance needs to mirror JIRA Server Fogbugz import tool

Problem:
Customer is migrating from Fogbugz On Demand to JIRA Cloud on a per project basis. The Fogbugz import for JIRA Server allows the mapping of fields that aren't available in the JIRA Cloud Fogbugz import tool.

Below you'll find the customers thorough walk through of the differences between the two import tool environments/mappings.

All screenshots have the Jira cloud importing Fogbugz OnDemand on the left and Jira server import Fogbugz SqlServer database on the right.

Screen 1 - Projects
This shows that both support individual project importing. However, you will see that server has one extra step as highlighted by the red underlines.

Screen 2 - Custom Fields
This shows the custom fields screen that server has. I do not care about this feature and have no need for it to be available for OnDemand import.

Screen 3 - Fields
This shows that the server adds three options for mapping imports that are not available with OnDemand. sFullName is the must have for us.

sCateogry and sPriority would be very nice to have, but I can deal with not having them.

Screen 4 - Values
This shows the ui for choosing what the mappings are. Once very nice thing with this is that the configuration file in the earlier steps remembers the mappings I created. So if I run through this for one of our projects we can use mostly the same configuration file for other projects. Also, since the configuration file is text I can write a script to do the user name mapping rather than having to fill in 400+ username ids .

Screen 5 - Links
This shows that the server adds two more link import options. The critical one for us is the duplicate case mapping. See also is nice but we don't actually intentionally use that much.