#Upgrade from 8.0 to 10 upgrade#
Jira might take longer to start after the upgrade If they don't affect your Jira instance in a significant way, you can use them with 8.0 even if they haven't been declared as compatible yet. Once you upgrade the test environment to Jira 8.0, you can try enabling the incompatible apps and see how they behave with the new version. We always recommend that you test the upgrade in a test environment. For more info on what you should do, see Preparing for the upgrade. Recommended actionsĭisable all incompatible apps, or upgrade them if they have compatible versions. Incompatible apps might block the upgrade and the Jira startup, because they're using elements that are no longer available or that have changed in the new version, like the Jira index, APIs, or some parts of the UI. You need to disable apps that are incompatible with Jira 8.0 or upgrade them to compatible versions, if these are available. Your upgrade won't be affected in any way it's just for saving you some time. If your Jira instance is small and an extra reindex doesn't sound like a problem, you don't need to disable it. =false Recommended actionsĭisable automatic reindex to avoid reindexing twice, and run the reindex manually, whenever you’re ready. After reindexing, the index will be compatible with any later version. That’s nothing to worry about, as you can rebuild the whole index by ‘reindexing’ Jira - an action you would probably run after a normal upgrade anyway. This change improves indexing (and searching), but it also makes your current index incompatible with the new version. One of the changes coming with Jira 8.0 is the upgrade of the Lucene library, which is responsible for the index in Jira. We've upgraded Apache Tomcat to 8.5.35 in Jira 8.0.2. For information on implementing the change, see Tuning database connections. Leaving the default of 20 can sometimes lead to “ResultSet Closed” errors during re-indexing on 8.x. If you're upgrading from Jira 7.x to Jira 8.x we recommend changing the pool-max-size parameter to 40 in your dbconfig.xml before the upgrade. Here's a summary of changes and important notes from Jira 8.0. Reduced logging to the catalina.out file.Decreasing heap size for Jira on 32-bit systems.Changes to several configuration properties.Zero downtime upgrade for Jira Data Center isn't supported.Jira might take longer to start after the upgrade.