we have JIRA 6.3.1 installed with projects, workflow and issue migrated from another defect tracking system. However we founf that some add-ons are not compatible and considering downgrade to 6.3 where it should be working. Can we do the downgrade on JIRA version only withour impacting current project, workflow and issue?
Technically, no, you can't downgrade.
In real life, as long as the database scheme has not changed AT ALL, then you can do it by hacking the versions of the data that the database is reporting and running an old Jira against it. 6.3.1 to 6.3.0 should be ok with that.
But I strongly recommend NOT doing it. A plugin not compatible with 6.3.1 but is ok for 6.3.0 is likely to be upgraded quite soon, saving you a lot of work - to do this downgrade, you're looking at a full set of export/downgrade/intensive-testing runs before you do it to production. It is likely to be a LOT easier to simply live with 6.3.1 and wait for the plugin update.
Or better, tell us what plugins are incompatible, and we'll see if you can work around it or if the authors are going to update soon!
I just downgraded our JIRA from 6.3.1 to 6.2.7 by exporting via JIRA backup, shut down the newer version, installed the older version and on first startup imported the backup XML file.
This procedure should work as long as the backup format has not changed between the affected versions. However, AFAIK Atlassian does not provide a compatibility matrix for the backup format. I'm still waiting for feedback from support confirming this.
Trial and error (on a test system) is a skill for all JIRA admins ;-)
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot