Issue Summary

Pre-upgrade check for MySQL 8 database in Plan your upgrade gives inaccurate warning, despite the database version should be supported.
Here are a few Confluence versions for comparison:

Confluence 8.5	MySQL 8
Confluence 9.1	MySQL 8 MySQL 8.4
Confluence 9.2	MySQL 8 MySQL 8.4

Indicates that this version of MySQL is supported and should stay this way for the immediate next Feature Release
Indicates that this version of MySQL is scheduled to be deprecated. This means the version is still supported now, but we highly recommend planning to upgrade it as the support will stop in the upcoming Feature Release

Version info

• Confluence 8.5.14
  This bug impacts a number of versions that supports MySQL 8. Confluence 8.5.14 is just an example used in this bug report.
• ATST 1.62.2
• MySQL 8.1.x, 8.2.x
  This bug impacts a number of versions of MySQL 8.x. MySQL 8.2.0 is just an example used in this bug report.

Steps to Reproduce

1. Install Confluence 8.5.14, connect it with MySQL 8.2.0
2. Go to General Configuration > Plan your upgrade
3. From the Upgrade to dropdown list, select a Confluence version that supports MySQL 8
4. Check the Pre-upgrade check

Expected Results

Pre-upgrade check should not report warning about unsupported database version

Actual Results

Pre-upgrade check reports warning about database version won't be supported.

Further Information

Here are the list of current behavior

Destination Confluence Version	MySQL Version	Pre-upgrade check result
Confluence 8.5.x	MySQL 8.0.0
Confluence 9.0.x	MySQL 8.0.0
Confluence 9.1.x	MySQL 8.0.0
Confluence 9.2.x	MySQL 8.0.0
Confluence 8.5.x	MySQL 8.2.0
Confluence 9.0.x	MySQL 8.2.0
Confluence 9.1.x	MySQL 8.2.0
Confluence 9.2.x	MySQL 8.2.0
Confluence 8.5.x	MySQL 8.4.4
Confluence 9.0.x	MySQL 8.4.4
Confluence 9.1.x	MySQL 8.4.4
Confluence 9.2.x	MySQL 8.4.4

Based on the above test results, the issue can either be from:

• The upgrade check didn't include MySQL 8.1, 8.2 and 8.3 as supported database despite it is supported
  OR
• The Supported Platform documentations should reduce ambiguity by specifying release number such as MySQL 8.0, instead of just "MySQL 8"

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available.