I have read through the JIRA Upgrade documentation but no where it is explicitly mentioned how we should handle the upgrade of plugin versions during an upgrade.
I have tried three options, let me know which one is preferable.
Option 1: Before you start upgrade, shut down JIRA and replace the old incompatible plugins with the new compatible plugins. Then proceed with Upgrade.
Option 2: Before you start upgrade, shut down JIRA and delete the old incompatible plugins. Proceed with Upgrade. After add the new compatible plugins through the UI.
Option 3: Proceed with upgrade with the incompatible plugins. Replace the plugins with compatible ones after the upgrade. This option has the drawback that it generates millions of lines of errors during upgrade and can mask any real issue.
I would go with option 1 whenever possible. If there are add-ons that are not available to upgrade to a compatible version until after the general JIRA upgrade, do it after the upgrade but before you allow general users to log in again. You can do this by modifying the group required for users to be able to log in to be an administrators group during the upgrade.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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