We're about to upgrade to the latest-and-greatest, but our IT is having doubts about the need to migrate databases between "old" and "new" JIRA.
So we're proposing to do it in a two-stage process: do the install/migration but leave old JIRA available to users while we confirm the new JIRA installation/migration has been successful; then sync the changes users have made in the interim to the new JIRA database before cutting the users over to new JIRA.
The question is: how do we do that "synchronization" step from old JIRA database to new JIRA database?
And the second question is: if GreenHopper affected by any of this?
All wisdom welcome,
Hi, an addition to what Ala said, do make sure the home directory is backed up and exported too, not just the database.
Greenhopper is just a plugin for JIRA. It'll move along with JIRA without any additional steps. You can update just as you update a plugin.
First, as about restoring, you may want to refer to the following link that gives a full description about the restoration process:
And if you want to use the database backup, you can backup your old jiraDB, then create a new empty DB and restore the old DB into the new one. After that, point your JIRA instance to the new (restored) DB.
As for the synchronization question, I think some related discussion about it was done here:
Lastly, for the greenhopper, can you elaborate further? As I'm a bit lost here. :)
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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