I would like to understand the pragmatics of Upgrading from JIRA 6.1 to JIRA 6.4 or JIRA 7.0
what are the drawbacks and what are the known issues, I see there is a recommendation on the Atlassian website to contact Migration Hub (https://confluence.atlassian.com/jira/skipping-major-versions-when-upgrading-jira-311920132.html) if we are upgrading to JIRA 7.0 so would like understand the implications if someone has
already upgraded to JIRA 7.0 and what are the Major benefits ?
I read from below link JIRA 7.0 enables Release hub, workflow triggers and others.
I would like to integrate Bitbucket to JIRA for evaluation (To implement CI workflow), currently running on JIRA 6.1, so any recommendations ?
Kindly share your experience for any such major upgrades you had done before.
CI workflow tools -> Git,Bitbucket,Jira,Bamboo,SVN-Mirror(for migrating from SVN).
From 6.4 to 7.0.x is a pretty straight forward upgrade. One brickwall i hit was a plugin that was not future proofed and that had to be disabled via the database to be able to start JIRA again. For that reason i would recommend you to verify that all plugins exist for the new version, and if not that you disable the plugins that does not have a 7.0.x version, only to reenable them once the server is started up.
This will allow you to run a few plugins that might not have been made for 7.0 but that are sufficiently compatible to still work, once re-enabled.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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