Description

In some occasions, it is possible that any newly created projects in Jira are not being associated with their default priority scheme and are, therefore, being created without any priority scheme.
This causes an issue described in the article Jira server throws jira-project-config-plugin error when editing the Priority Scheme of a new project.

Usually, this is caused by the third-party plugin Project Configurator, however, it would be interesting if Jira could identify this behaviour and fix it automatically or notify the customer about it before causing an issue.

Environment

• Jira Server 8.5.0
• Usually coming from Cloud migration, or after a project migration using the Project Configurator plugin (which is recommended by Atlassian in a few documentations)