The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Roll back due to Jira Agile minimum requirement

John Ferlito
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 26, 2016

This question is in reference to Atlassian Documentation: This version of JIRA Agile requires a minimum build number of #45 in order to proceed

Do I have to roll just the plugin version back, if so how?

Or do I need to roll back the Jira version, if so this doesn't work as it complains about DB versions

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
February 27, 2016

You can't downgrade a JIRA systems, and it can be risky downgrading an add-on if the versions you cross have made database changes (because they can't be reversed)

To downgrade an add-on, download the version you want to go to and install it via the "upload add-on" link.  If the data has changed, you'll get errors, but most addons will fail in a way that means you can just go back to the version you downgraded from.

In this case, you won't be having that issue - your attempt to upgrade Agile has simply stalled, and although you might have 7.x installed, it won't have made all the changes it needs to.  Just install Agile 6.7 with the upload add-on link, and it'll pick up the upgrade fine.

TAGS
AUG Leaders

Atlassian Community Events