EAP to prevent dupliate is causing the migration to fail

XMLWordPrintable

    • 6
    • Severity 3 - Minor
    • 12

      Issue Summary

      Customers that are using the EAP to prevent duplicated and have team managed projects on the destination, are not able to migrate.

      It seems that the conflict entity feature does not support team-managed projects.

      Steps to Reproduce

      1. Create project in server
      2. Create project team managed project in cloud
      3. Ensure conflict with entity between server and cloud (e.g. both projects have issueType “Task”).
      4. Run duplicated entity check
      5. In CSV enter resolution as TARGET for team managed project entity
      6. Run migration
      7. Observe import failures during migration.
      8. Import errors can be verified using JCMA logs

      Expected Results

      The migration is completed.

      Actual Results

      The below error is showed on the logs.

      2025-07-14T02:04:57 ERROR ABC project-import Jira failed to ingest entity Issue Type Scheme 'ABC: Scrum Issue Type Scheme'. Reason: IllegalScopedEntityArgumentException: Illegal Entity Scope for Entity class (ISSUE_TYPE). Expected entity scope 'GLOBAL' but has scope 'PROJECT'. This caused 78 other item(s) to fail

2025-07-14T02:05:04 ERROR ABC project-import We couldn't import Project ABC. Reason: IllegalScopedEntityArgumentException: Illegal Entity Scope for Entity class (ISSUE_TYPE). Expected entity scope 'GLOBAL' but has scope 'PROJECT'. This caused 77 other item(s) to fail

2025-07-14T02:05:07 ERROR ABC project-import We couldn't import Project Role Association 503b70fc-7e09-47d7-8f97-b6dedb7a5756. Reason: jira/classic:issueTypeScheme:10300. This caused 0 other item(s) to fail

2025-07-14T02:05:07 ERROR ABC project-import We couldn't import Project Role Association 63485ed0-371c-4cc7-8e0b-bf4d56e52f7d. Reason: jira/classic:issueTypeScheme:10300. This caused 0 other item(s) to fail

2025-07-14T02:05:07 WARNING ABC project-import We couldn't import Project Version 'Version 1.0'. Reason: jira/classic:issueTypeScheme:10300. This caused 16 other item(s) to fail

2025-07-14T02:05:07 WARNING ABC project-import We couldn't import Project Version 'Version 3.0'. Reason: jira/classic:issueTypeScheme:10300. This caused 2 other item(s) to fail

2025-07-14T02:05:08 WARNING ABC project-import We couldn't import Project Version 'Version 2.0'. Reason: jira/classic:issueTypeScheme:10300. This caused 25 other item(s) to fail

2025-07-14T02:05:22 ERROR ABC project-import We couldn't import Issue ABC-1. Reason: jira/classic:issueTypeScheme:10300. This caused 0 other item(s) to fail

2025-07-14T02:05:22 ERROR ABC project-import We couldn't import Issue ABC-2. Reason: jira/classic:issueTypeScheme:10300. This caused 0 other item(s) to fail

2025-07-14T02:05:22 ERROR ABC project-import We couldn't import Issue ABC-3. Reason: jira/classic:issueTypeScheme:10300. This caused 0 other item(s) to fail
etc...

      Workaround

      • Update CSV to remove TARGET from all entities that match against team managed projects (note: there is no easy way to identify team managed entities from company managed entities)
      • Run migration
      • Observe successful migration

            Assignee:
            Rogério Prando
            Reporter:
            Guilherme A
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: