I got an instance health check warning about my SQL Server database not being compatible with JIRA 7.3.1 after upgrading from 7.2. The one thing I noticed is that instance health check was not checking for SQL Server in 7.2 and now it is. Should I be worried about this?
I really do NOT want to switch database and would downgrade to 7.2 if I have to.
It's not supported on 7.2 either, you're just getting a proper warning that you are unsupported now.
A downgrade would make the message go away, but
So, I wouldn't bother. You should swap to a supported database, or accept that you're unsupported on the current version.
Ah, that's good.
Moving to another database is usually moderately simple. Have a look at https://confluence.atlassian.com/adminjiraserver073/migrating-jira-applications-to-another-server-861253107.html . It's about moving the whole system to new servers, but if you ignore all the stuff about the application server, the stuff about database server moves is in there.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs