It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

upgrade trouble, from 7.2.2 to 7.3.3 and back to 7.2.8

since we had add-on compatibility problems had to revert back to 7.2.8 from 7.3.3


Used the 'jira.downgrade.allowed=true' option and things seemed ok, for a time.

Now we notice the good ol' "JIRA Software is licensed but not currently installed" problem.

we're a standalone type system installed from tar.gz archive.

I would think the code is actually the correct version, problem seems to be this table in the DB, 'pluginversion' has some bad values in it that didn't get set back to 7.2.8

Anyone know the correct values for these records in 7.2.8 ?

image2017-3-17 15:37:6.png


well, actually, home_jira/plugins/installed-plugins DOES contain:


and the 7.3.0 language packs

If I just delete them and restart jira, will it repopulate the dir from the 'software' directory ?

3 answers

  1. Revert to the backup you hopefully took before upgrading. Database dump, JIRA_INSTALL directory and JIRA_HOME directory.
  2. Since the difference between 7.2 and 7.3 contains some added project permissions etc. It might be so that you need to approach this differently because there might be compatibility issues.
  3. Can you live without these plugins and are you sure they will not function on 7.3.3 or any of the version released under 7.3.X?

You can see a XML export and import approach in

Good luck!



unfortunately the 'issues' with the upgrade were not spotted immediately and people have been using the app all day now. fixing it without reverting to backup is the top priority.

We're fine with waiting at 7.2.8 until incompatible add-ons have been updated to work with 7.3 era code

Problem is the "JIRA Software" core component is installed as a plugin and it's the 7.3 jars and wont work with the rest of JIRA at 7.2.8

I can probably remove the 7.3 jars and replace them with the 7.2.8 jars in


and manually edit the version strings in the DB



YES, this worked fine.


We had the same issue...
downgrade from 7.13.5 to 7.10.1

what we did to resolve:

  • create pg_dump of db from jumpbox

  • create xml backup of jira

  • stop jira

  • point jira to old /opt/atlassian/jira
    • was sym linked, but removed the sym link as recommended by Atlassian
  • Create /var/atlassian/application-data/

  • moved all plugins from 
    to a backup dir
  • start jira
  • install JSW and JSD
  • install all plugins
  • restart jira
  • reindex

all good - 1hr 5m from start to QA approved

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira

The add-in you’ve been waiting for: Jira Cloud for Excel 🙌

Introducing Jira Cloud for Excel Here at the product integrations team at Atlassian, we are thrilled to announce the new Jira Cloud for Excel add-in! This add-in lets you export Jira data directly ...

971 views 10 25
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you