I am trying to import mantis bugs into Jira. I need to import on a project to project basis. Is it possible? From what i have read, the documents state that the all of the existing data gets overwritten. I have already setup users, groups, roles and other projects on my Jira OnDemand. For now i only need to import bugs related to a specific project from mantis.
Please let me know your thoughts.
JIRA Importers Plugin (bundled with JIRA) allows you to import selected Mantis projects into selected (existing or auto-created) projects in JIRA.
If users match in both systems - they will be reused. Groups and roles are not touched during the import.
The only problems is that you seem to want to import into JIRA OnDemand. That would theoretically require you to expose your Mantis DB to the public internet. And I am not sure if OnDemand platform by default supports connection on non-http(s) ports to outside word - in this case you would need to talk to Atlassian Support.
Generally speaking JIRA Importers Plugin is only entering OnDemand worlds and there are several limitations customers and support personnel have to deal with.
The alternative which you could consider is: exporting your data from JIRA onDemand to XML dump, installing (that's dead simple with new installers) JIRA locally (using evaluation license), importing the XML dump to your local JIRA (so that you have all these projects, users and groups set up), running Import From External System and performing the import from your local Mantis instance.
After you are happy with the results (import process is quite configurable so you can end up with different things depending on how you configure the process), then export your JIRA data to XML dump localy and import it back to JIRA OnDemand (the latter my involve raising a support request with Atlassian (OnDemand project) as I don't think you will have access rights to do it on your own).
JIRA Importers Plugin imports all attachments as well (provided that you swtiched on Attachments in your JIRA instance).
If you decide to use temporary local JIRA instance to perform the import and only then upload the results (as XML dump) to OnDemand, then please keep in mind that attachments are not part of this backup, but have to be manually copied (usually from <JIRA HOME>/attachments directory.
So after you finish the import you will be able to find all your Mantis attachments in this directory - stored as files in subdirectories for each project. Easy and intuitive. You may zip it and attach to a support request you will create.
When using CSV import plugin, i can see a "attachment" as Jira field in the Setup Field mapping. What sort of value does this field accept, does it accept an image/binary content or does it accepts a path? If it accepts path, how do i set the value for path? How do i make sure that the attachment is associated with the correct bug, does the name and type of attachment helps in any way ?
It does accept URLs, but not ones which use file:// protocol due to security reasons (one could steal any file from the server which JIRA process can access). So if you prepare your CSV file with attachments using http and https URLs then you need to expose your attachments obviously via HTTP or HTTPS. There are several easy or more complicated ways to go: from shared web drives, through setting up Apache on making it serve your attachments or (if you don't mind your attachments to be theoretically public for a while) using services like Dropbox.
Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...
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