Problem
Several exceptions in JIRA log, usually about not being able to create a scheme containing "default" in the name.
Examples
java.util.concurrent.ExecutionException: com.botronsoft.jira.rollout.impl.merge.MergeException: Unable to apply change 'type: addition, object: JiraConfigurationRoot#root/JiraPermissionScheme#default software scheme Caused by: com.botronsoft.jira.rollout.impl.merge.MergeException: Unable to apply change 'type: addition, object: JiraConfigurationRoot#root/JiraPermissionScheme#default software scheme, target object: JiraConfigurationRoot#root, feature: permissionSchemes Caused by: com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericEntityException: Could not create Permission Scheme with name:Default software scheme as it already exists. |
Also applicable for Notification Schemes.
Cause
CMJ finds matching configuration objects for the snapshot on the target system. Usually configuration objects are matched by their name (or key for projects, name+type for custom fields, etc.). However for default schemes CMJ always tries to match the default scheme from the snapshot to the default scheme on the target disregarding the name
It seems that you have a scheme in the snapshot that is named with the same name as the default scheme on the target, where it is probably not default ("default software scheme") – this way they don’t get properly matched and a new scheme is trying to be created unsuccessfully. We have an issue open for this case - CMJ-97
Resolution
The best known workaround is to just rename the scheme on the source JIRA and deploying a new snapshot without a scheme with the same name as the default on the target that isn't default.