I am about to begin refreshing our JIRA Dev enviornment with a mysql db dump from our Prod enviornment. Our Prod env is running mysql 5.5 while our Dev env is running mysql 5.6. Are there any issues I should be aware of before attempting to perform this data refresh? Snapshopts have been taken of both systems.
5.5 and 5.6 are similar enough that you shouldn't encounter any differences as far as JIRA is concerned.
If you were restoring to a MySQL 5.7 instance (now supported in JIRA 7.3 and higher), then there is a possible new permission required by the SQL user in that version of MySQL. https://confluence.atlassian.com/jirakb/com-mysql-jdbc-exceptions-jdbc4-mysqlsyntaxerrorexception-references-command-denied-to-user-872266070.html explains this, but I don't think you will be effected by this until you go to a MySQL 5.7.6 version or higher.
It might be also worthwhile to update the mysql jdbc driver JIRA is using to be able to connect to that database type. You can download the latest version from https://dev.mysql.com/downloads/connector/j/ You don't normally need to do this with high frequency, but if you're on an older version of JIRA, or a system that has been upgraded from much older versions over time, it's easy to overlook this file. This file isn't something JIRA can update, so it's probably worth doing this at the same time you perform other maintenance on JIRA. Some of the older versions of this driver were known to have performance problems or bugs that have been largely resolved with these more recent versions.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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