I recently moved my JIRA installation to a new server. I thought I had pointed my new installation at the existing database (on a remote server accessible by both old and new JIRA installations), but instead I pointed the new JIRA at an older, stale, copy of the database.
It's now been about 2 months, and of course we're missing issues – those that weren't in the stale database copy.
We're using MySQL, in case that matters.
There is no easy solution I am afraid!
You cannot copy the issues from on DB to another. There will be lot of missing pieces.
Depending on how many issues you lost vs how many were created since the migration, you need to start from the old instance or current instance. You can then setup a second instance pointing to the other DB and move issues that are missing.
Identifying the difference is not an easy thing either. You can probably do it easier on the current instance because you can find issues created since a given date. Once you identify the missing issues, you can export them into CSV and import them into the other instance. You will loose some history and dependencies. And the issues will get a new number. But it will still be better than nothing!
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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