Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×We will be upgrading Jira from 6.4 to 7.0 on our Jira dev environment. Does upgrading to 7.0 require increase in memory? Also we bought few more licenses and have a total of 2000 any suggestions on increase in memory size?
While going through documents i found two methods for upgrade "Fallback Method" & "Rapid upgrade method". Which method is preferable?
How much time will or should it take to upgrade Jira 6.4 to 7.0?
From our experience 7.2.8 consume less resources than we used with 6.4. we haven't increase jvm setting at all
You won't need more resources to run Jira 7, it's similar to 6.4 in terms of load.
You can't buy 700 licences, that's not a valid tier, so I'm not sure what you've done there. Could you explain which tier you were on and what you've moved to?
The method of upgrade is not really something we can advise on from just "6.4 to 7". Have a look at the upgrade guide, as they're both described in detail to help you decide which is better for you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Juby,
The first thing you'll want to do is verify how much memory you have allocated to your instance and then use the JIRA Sizing Guide to determine the proper amount of heap and physical memory you need to allocate to your instance.
Once you believe you have the proper amount of memory, you'll want to make sure your add-ons are compatible with the version of JIRA you're upgrading to.
In regards to which method to use we provide multiple methods so you can make the determination which is best in your environment. Regardless of which method you chose make sure you backup your instance first, preferably with native db tools. Here are some criteria for the Fallback vs Rapid Upgrade:
Upgrading JIRA with a fallback method
High / Mission Critical
This method is recommended for enterprise environments where extended or unplanned downtime might negatively impact the business.
Upgrading JIRA using a rapid upgrade method
Low – Medium
If you use JIRA in a non-mission critical environment, depending on your specific installation details, you use either the safe (no downtime) or manual method to upgrade.
Cheers,
Branden
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.