I'm about to upgrade from 4.4.3 to 5.2 Jira and migrate it to a new server. In short, our company was bought and we need to move Jira to their corporate infrastructure which I have little control over. Therefore I need to put together a fairly detailed plan to upgrade and migrate our server. I have several projects, each with its own custom workflow using groovy runner scripts for validators, etc. I have edited velocity email templates and have numerous custom fields. If I have read the Jira upgrade documentation correctly, before I import the data from my 4.4.3 server, I need to ensure the new 5.2 server has the
- same workflow and workflow schemes
(Action: export 4.4.3 workflow and import it into 5.2 hopefully?)
- velocity email templates
(Action: hopefully just copy the appropriates 4.4.3 files into 5.2?)
- as for the rest of the customizations (priorities, statuses custom fields, etc)
(Actions: these must be manually recreated -- this sucks big time!!!!)
The big question: Am I correct in my above assumptions, or is there a simplier way?
BTW, you can have all my karma points if you make my life much easier.
Could you explain something here - it sounds like you are trying to merge two Jira installations here (in which case your email velocity changes will break the target Jira install, so you'll need to put more thought into that). Is that correct?
If it's not, and you're simply picking up your data and putting it into a new, empty Jira, then the process is a lot more simple - Jira can upgrade it automatically, and you will only need to merge in your velocity changes.
Sorry for taking so long but simply importing the XML did bring along the workflows, custom fields, etc. Still need to copy over my velocity changes and change most of the userids to conform with the new company's LDAP but that's another 10 year old Jira issue.
I need to ensure the new 5.2 server has the...
Looks like a 5.2 installation is already there and you need to merge your existing 4.4.3 data into that. Since you seem to have little control over the new 5.2 installation, let me tell you what are the possibilities of customization.
One final word on all the aspects: Deciding of these changes in the target JIRA is a management thing. You need to convince your management with the exact requirement and plan the migration first. Some of the functionalities of your current installation may not be available after the migraton to the new instance, and also in the target JIRA there will be changes that its systems administrators have to live with.
Request for a test replica instance of thetarget 5.2 install and study it. It will make it easier for you to identify what is possible and what is not.
After you finalize all the aspects, here's my suggested plan for upgrade/ moving:
None of the customizations needs to be manually imported. They will be ported along with the data. But you will have to merge in the changes like changes to velocity templates, jsp files etc.
Follow this process in a test server - use the upgrade your existing JIRA option.
After upgrade, merge in the changes to velocity templates, modify the grrovy scripts to accomodate API changes and do some testing.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Hi Atlassian Community! My name is Shana, and I’m on the Jira Software team. One of the many reasons this Community exists is to connect you to others on similar product journeys or with comparabl...
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