I am writing you because I have some questions:
First of all, Do you have any document or procedure in order to migrate from Jira V3.12.2 to V7.3.0 without losing any kind of information I mean, files attached to the Ticket or all the tracking information that is joint to the ticket?, Is it possible? What do we have to do?
I look forward to hearing from you soon.
You have to upgrade to each version in turn. 4.0, 4.4, 5.2, 6.3, 6.4, 7.0, 7.3 off the top of my head. It is ten years worth of changes, which means it is a pretty different app.
You might be better off persuading people to leave the old 3.12 instance alone, making the projects read-only. And install a new 7.3 instance.
Sounds like you will resurrect a dinosaur, or? Just kidding.
First of all backup the data before and after each upgrade step. Next you have to read the release notes for all of the upgrades, at least for the majors (4,5,6,7). Beginning from version 5 (as far as I remember) things will get easier, since Jira is able to update its DB itself without the export/import dump procedure. As soon as you have reached 6.4.14 you can jump to 7.0.<latest> and then to any other >=7.1.0.
Hints: Perform the integrity checka after each step. Select some reference issues that you also compare after each step.
And last but not least, I wish you good luck and endurance.
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