/
Resolving Duplicated Issues and Fields After Snapshot Deployment in CMJ

Resolving Duplicated Issues and Fields After Snapshot Deployment in CMJ

Summary

This article addresses a known issue where duplicate issues or fields appear after a snapshot deployment using Configuration Manager for Jira (CMJ) in Jira Data Center. The problem often results in:

  • Duplicated custom fields are showing in screens.

  • Application error: IllegalArgumentException: Multiple entries with same key

  • Confusion during deployments due to unresolved field mappings

Error Screenshots

image (13).png
image (14).png

Problem

After deploying a snapshot from one Jira instance to another, the following issues were encountered:

  1. Custom field with ID customfield_10330 appeared multiple times in screens Rendszer Issue Screen Hiba.

  2. Error:

    java.lang.IllegalArgumentException: Multiple entries with same key

  3. The UI displays duplicate field entries in screen configurations and field configurations. This typically occurs due to unresolved custom field conflicts or missing mappings during the deployment process. In CMJ, this situation can occur if the same custom field name/type exists in both source and target environments, but is not properly reconciled during deployment.

Cause

This happens when:

  • The same custom field exists in both source and target with different internal IDs.

  • The field was not mapped correctly during the Resolve Custom Field Conflicts screen.

  • CMJ defaults to Create new field if a matching field isn’t selected.

  • Multiple fields with the same name exist after deployment, leading to conflict in internal mappings and UI duplication.

  • A snapshot was re-deployed without cleaning up the previously deployed artifacts.

Solution

  1. Run an Integrity Check

    1. Run CMJ’s built-in integrity check to identify misconfigured or duplicated fields:

    2. Go to CMJ > Integrity Check

    3. Select System Scope

    4. Review violations:

      1. Duplicate custom field

      2. Inconsistent screen schemes

      3. Field mapping issues

    5. Reference: Integrity Check Guide

  2. Identify and resolve custom field conflicts

    1. In CMJ, re-import the snapshot but pause at the “ Custom Field Conflict Detection” screen.

    2. For the field, ex, customfield_10330 or other duplicates:

      1. Do not leave the default Create new field selected unless a new field is intended.

      2. Use the drop-down mapping table:

        • Left: fields from snapshot

        • Right: select the corresponding field from the target

      3. Map based on name, type, and expected usage.

Guide: Resolve Custom Field Conflicts

  1. Clear duplicates in Jira

If duplicate fields already exist:

  1. Go to Jira Admin > Custom Fields.

  2. Search for duplicates with the same name (e.g., “Rendszer”).

  3. Delete duplicates after:

    1. Verifying they are not used in any active screens, workflows, or issues

    2. Backing up configurations

  4. If a field is in use and cannot be deleted:

    1. Rename it temporarily to avoid confusion

    2. Remove from all screens

    3. Mark as inactive