Problem Definition

Currrently, in Connecting Jira applications to MySQL documentation, we provide the MySQL permission configuration for "For MySQL 5.5, MySQL 5.6, and MySQL 5.7.0 to MySQL 5.7.5" first before "For MySQL 5.7.6 and above":

For MySQL 5.5, MySQL 5.6, and MySQL 5.7.0 to MySQL 5.7.5:

GRANT SELECT,INSERT,UPDATE,DELETE,CREATE,DROP,ALTER,INDEX on <JIRADB>.* TO '<USERNAME>'@'<JIRA_SERVER_HOSTNAME>' IDENTIFIED BY '<PASSWORD>';
flush privileges;
For MySQL 5.7.6 and above, you must also include the REFERENCES permission:

GRANT SELECT,INSERT,UPDATE,DELETE,CREATE,DROP,REFERENCES,ALTER,INDEX on <JIRADB>.* TO '<USERNAME>'@'<JIRA_SERVER_HOSTNAME>' IDENTIFIED BY '<PASSWORD>';
flush privileges;

If a user configured the permission for 5.7.5 in MySQL 5.7.6, certain feature such as project creation will silently fail.

Suggested Solution

Update the Connecting Jira applications to MySQL documentation so the permission configuration for "MySQL 5.7.6 and above" is listed above "MySQL 5.5, MySQL 5.6, and MySQL 5.7.0 to MySQL 5.7.5" permission configuration.

This way, if a customer configured the MySQL permission meant for 5.7.6 in MySQL 5.7.5 and lower, he/she will see an error from the UI and the user can apply the correct permission.

Workaround

Apply the correct permission based on the version of MySQL provided in Connecting Jira applications to MySQL