Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...


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

...