Depending on your version of MySQL, you may need to change the storage engine parameter specified in your dbconfig.xml file. The following is seen on the logs:

JIRA-Bootstrap WARN [c.a.j.appconsistency.db.MySqlConnectionUrlCheck] You have an error in your dbconfig.xml file. Missing "default_storage_engine" in connection url. The "storage_engine" parameter is deprecated and should be replaced with "default_storage_engine"

This should only be required if you've upgraded your MySQL database, and tried to use an existing dbconfig.xml file. The dbconfig.xml file (located at the root of your JIRA home directory) defines all details for JIRA's database connection. This file is typically created by running the JIRA setup wizard on new installations of JIRA, or by configuring a database connection using the JIRA configuration tool.

The storage engine parameter should be:

• storage_engine - for versions of MySQL below 5.7
• default_storage_engine - for versions of MySQL of 5.7 and above
    Make sure the JDBC driver is upgraded to the latest version!

jdbc:mysql://dbserver:3306/jiradb?useUnicode=true&characterEncoding=UTF8&sessionVariables=storage_engine=InnoDB

jdbc:mysql://dbserver:3306/jiradb?useUnicode=true&characterEncoding=UTF8&sessionVariables=default_storage_engine=InnoDB

To edit your dbconfig.xml file:

1. Locate the dbconfig.xml file at the root of your JIRA home directory, the default locations are:
   1. C:\Program Files\Atlassian\Application Data\JIRA (on Windows) or
   2. /var/atlassian/application-data/jira (on Linux)
2. Open the file in a text editing program.
3. Change the storage engine parameter to the appropriate value.
4. Save the file.

You should now be able to start JIRA.

For further details on setting up Jira with MySQL 5.7 please see Connecting Jira applications to MySQL 5.7