I would like to upgrade my jira version 4.0.2 to lastes 6.2. without losing any data because a large volume of data exists in my system and for this upgradtion which upgrade process should I need to follow.
My current Database Statistics are given below:
I have no experience to jira upgrade.
Could you please inform me proper guideline with any resource link?
I would greatly appreciate your help.
Start with the obvious - read the Atlassian documentation for upgrading Jira. https://confluence.atlassian.com/display/JIRA/Upgrading+JIRA It's short, but links to a lot more detail.
The numbers you've given imply that you need to do some housekeeping and look at your business processes (1277 custom fields and 200 workflows is often a big red flag that things are disorganised), but they don't cause any upgrade related concerns.
I also highly recommend reading all the release notes for major/minor releases (skim the bugfix/point releases), so you'd want to read 4.1, 4.2, 4.3, 4.4, 5.0, 5.1 etc
As you have stated -
The numbers you've given imply that you need to do some housekeeping and look at your business processes (1277 custom fields and 200 workflows is often a big red flag that things are disorganised), but they don't cause any upgrade related concerns
I completely agree with you, but at the same time I am curious to know any "green" flag benchmark statistics out there about large JIRA installations
Depends on the size, but I'd worry about any installation with more than 200 custom fields or 20ish workflows (That excludes Agile "simplified workflows" though. If you're hand-designing 200 different processes, you're doing something very wrong).
I'm not sure there are any positive greens - it depends on what the system is being used for before you can say stuff like "lots of projects good" or "small handful of projects good"
First of all take backup of your data, also if you are using lot of plugins and their customization in your JIRA then it's a very high chance that you run into compatibilty issues as JIRA 6.x has very diff. APIs and design guidelines as compared to 4.x, thus while installaing the jira 6.x choose the upgrade option and test thoroughly that all data has been migrated.
Custom fields and customized scripts(if using scrip runner) can also give some pain.
Hi Tarun and Nic,
Thank you for your quick response.I can backup jira data in a portable XML format but attachment will not backed up and I need to do this in manually.
Can you please tell me where all attachments are store in jira installation directory or which folder should I need to backup for attachments backup?
You should use whatever database backup tools are appropriate for your database server, and if there's more than one, use the one you are most comfortable/familiar with.
All you need is the ability to take a copy of the Jira database and be able to reload it on another database. (Plus, a copy of the attachments of course)
Thanks for your reply.
I have a query regarding plugin.I already using a third party plugin "JIRA Suite Utilities - 0.7.0" for additional set of workflow conditions, validators.If I upgrade from 4.0.2 to latest then do I need to install this plugin again to upgrade version?
You'll need to read the release notes for ALL your plugins, as they will ALL need upgrading for that sort of a jump. For smaller jumps, some of them won't need updating, but 4.x -> 6.x is a very large step. (Some may also be removed or become useless to you, you'll need to read up to find out which)
Basically Nic got much of it covered, but just to share my personal advise normally I have given to customers:
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
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