Tested again to ensure that nothing went wrong. Note that there are a migration of the configuration when you upgrade to JIRA 11.0.0, so if the migration is not executed we can expect that something are broken.
Note that at the end of the migration a page with the reference JIRA.JIRAConfigAuthMigration is created (to avoid that the migration is executed multiple time). So in the standard process when you upgrade to JIRA 11 a listener would process of the data migration. But if you install JIRA 11 and then reinstall JIRA 10 and then upgrade it could happen that the migration is not executed (because the migration document already exist). Could you check in the log that this log message Running migration of JIRA configuration was written at some point ?
Note you can also re-run the migration just by dropping the JIRA.JIRAConfigAuthMigration document and rebooting the wiki.
Best regards
Josué
This message was sent by Atlassian Jira (v9.3.0#930000-sha1:287aeb6)
If image attachments aren't displayed, see this article.
