We are in the process of upgrading Jira from 7.0.2 to 7.4.2 and at the same time migrate from the built in database to a postgresql database.
As per documentation is simply seems like:
- Export config/issues in admin area
- Stop Jira
- Upgrade Jira
- Remove dbconfig.xml
- Start Jira
- Config new postgresql connection
- Import config/issues in admin area
- Done (?)
However this doesn't work for us. Whenever we try to do it like this we get the following error: https://confluence.atlassian.com/jirakb/error-when-logging-in-or-visiting-dashboards-864653761.html
However none of the issues applies to our setup. We have no application links and we only have one dashboard (default system).
It seems to me when the upgrade takes place, it doesn't alter all tables in the database?
Note that simply migrating from 7.0.2 builtin database to postgresql (still Jira 7.0.2) doesn't have this problem.
That is not what the documentation says.
You have two *separate* tasks here. Upgrading a system, and changing the database. In terms of time, you might well be doing them in one go, but there are two processes.
Your steps will perform two upgrades. One of them is redundent and the other not the recommended way to do it, and is probably the cause of the problems you're having.
You should migrate first by exporting and importing the xml. Then upgrade the migrated system. You could do it the other way around, but the built-in database is not a production class solution and it's prone to fail during complex actions like upgrades.
Thanks for you reply, Nic. I'm unsure what you're trying to say. Migrating from H2 database to postgresql is OK (documentation I followed is here, https://confluence.atlassian.com/adminjiraserver071/switching-databases-802592192.html) - Jira works fine.
When I then proceed to upgrade Jira from 7.0.2 to 7.4.2 I get the issue described in OP. Followed documentation https://confluence.atlassian.com/jira/upgrading-jira-using-a-rapid-upgrade-method-312738529.html
I've tried doing the task both seperately and combined, same result both times.
The process you posted originally went:
Your comment now says you're doing it in the best order now, so that concern has gone away.
What does the SQL in the KB article tell you?
Can a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...
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