One of our projects has its issues stored in Mantis. Our Mantis instance runs on an externally hosted web site with PHP and MySQL. It is not on a machine where we can install JIRA or other tools. The Mantis instance has:
Many of our source control commit messages mention these Mantis items by number.
We use JIRA OnDemand for various other projects here, and want to move this large project from Mantis to JIRA. We use the JIRA OnDemand hosted service, which doesn’t allow installing arbitrary software/plugins, such as the JIRA Mantis import tool.
Because of the numerous mentions in our source history and other places, we would like very much to preserving the old mantis issue numbers as JIRA item numbers.
Here is what we have in mind to perform the migration.
What about attachment? Will this process bring along the attachments? Or do we need to handle those some other way?
This is a relatively complex series of steps, so we would appreciate feedback on our current plan that is based on what we find documented in JIRA online discussions, wiki pages, etc. It still seems to us there are a lot of steps that could introduce problems or cause the loss of data. If there is a more efficient and direct route for this process we would like to consider it.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
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