/
Deployment Failure During Configuration Analysis while CMJ Cloud to Cloud Migration.

Deployment Failure During Configuration Analysis while CMJ Cloud to Cloud Migration.

Description

Users reported a failure during the analysis phase while deploying project configurations using Configuration Manager for Jira (CMJ) Cloud from Sandbox to Production and vice versa. The issue was consistent across environments despite previous successful deployments.

Diagnosis

During deployment analysis, CMJ creates HTTP 400 errors due to issues interacting with the Jira Cloud REST API. The errors are linked to:

  • A workflow name containing an invalid character.

  • A missing group reference (CMJC-CreateSharedObjects) used for permission grants.

image-20251022-060250.png

Cause

Invalid workflow name

The workflow "ITS: \tCompany Control request workflow" contained a tab character (\t), which is invalid according to the Jira Cloud REST API specifications.

Missing group reference

CMJ attempted to assign permissions to a temporary group (CMJC-CreateSharedObjects), but it was either missing or deleted, resulting in a Group does not exist error.

Solution

Fix the invalid workflow name

  1. Go to the source Jira Cloud instance.

  2. Navigate to Jira Settings > Issues > Workflows.

  3. Locate the workflow with a tab character:

    ITS: <tab>Company Control request workflow

  4. Remove the tab and rename the workflow to:

    ITS: Company Control request workflow

  5. Save and publish the workflow.

  6. Re-run the analysis in CMJ. The error should be resolved.

Resolve the missing group issue

  1. Navigate to CMJ > Manage Deployments > Analyze Changes.

  2. Identify and remove references to the missing group CMJC-CreateSharedObjects.

  3. Go to CMJ > Advanced Settings in both source and target environments.

  4. Use Clear Cache or Refresh Metadata to refresh CMJ's internal state.

  5. Re-trigger the analysis. CMJ will automatically recreate the necessary temporary group.