What's the best/safest way to downgrade Greenhopper plugin?

[Justin Corcoran]

I (stupidly) upgraded the GreenHopper plugin from 5.9.3 to 5.9.6 in our production environment without first testing it in a sandbox environment. I really don't like that the details of an issue are shown next to the columns on the rapid board, instead of on top of most of the columns, and it doesn't look like this is a configurable option. Therefore, I'd like to roll back to version 5.9.3. I've downloaded the jar for that version, but I'm not sure how best to downgrade.

In our sandbox, I upgraded to 5.9.6 (so it matches the prod instance), uninstalled GH, and then uploaded the jar and installed it. However, I got a message saying GH was unavailable, and may be upgrading. This didn't go away after several minutes, although GH appeared to be all good on the admin screens. I stopped and restarted JIRA, no help. The only way to clear the error was to upgrade to 5.9.6.

So, the question is, what am I doing wrong? What's the proper procedure for downgrading GH?

[Nic Brough -Adaptavist- · Accepted solution]

I don't think there is a way to downgrade. I suspect you've got two basic options

1) Install the old version in a dev environment, put in a spot of test data, check what tables it's using in the database, then upgrade it and see what data migration the upgrade does. Also, check the indexing and the rest of the Jira home directory to see if it does stuff there. Then work out how to reverse it with edits and SQL

2) Raise a support request with Atlassian. They might not help directly, but they could tell you a lot about my first suggestion.

[Justin Corcoran]

I'll enter an issue with atlassian, thanks!

[Matt]

Have you tried to uninstall and install other version by uploading old jar whith GreenHopper 5.9.3?

[Nic Brough -Adaptavist-]

I don't think there is a way to downgrade. I suspect you've got two basic options

1) Install the old version in a dev environment, put in a spot of test data, check what tables it's using in the database, then upgrade it and see what data migration the upgrade does. Also, check the indexing and the rest of the Jira home directory to see if it does stuff there. Then work out how to reverse it with edits and SQL

2) Raise a support request with Atlassian. They might not help directly, but they could tell you a lot about my first suggestion.