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. |
Cause
'Default software scheme' is not really default.
Most often this is caused by schemes with the same name in the snapshot and the target instance, one of which is default, while the other is not.
For some object types, CMJ matches default objects in the snapshot to their default counterparts in the target instance. Those include permission schemes, issue type schemes, notification schemes, field configuration schemes, field configurations, workflows. Non-default objects are matched by name. If a matching object is not found in the target instance, a new one will be created using the name of the object in the snapshot.
Resolution
- If you'd like the permission scheme in the snapshot to match the one in the target instance, make sure they are either both default, or that they are both non-default and have the same name.
- To make sure the default scheme is not exported, create a copy of it and assign it to the exported projects. Rename it if necessary.