Non-existent issuetypes are present in the Jira Cloud instance after migration via JCMA

XMLWordPrintable

    • 1
    • Severity 3 - Minor

      Issue Summary

      In some instances that have been migrated from Server to Cloud via JCMA, it is possible that non-existent issue types persist and these issue type IDs are returned in Rest API responses.

      Steps to Reproduce

      • Migrate the instance from server to cloud via JCMA
      • Validate if non-existent issue types are returned in the below API endpoint responses:
        a) GET /rest/api/3/field/customfield_<id>/context/issuetypemapping
        b) GET /rest/api/3/issuetypescreenscheme/mapping
        c) GET /rest/api/3/fieldconfigurationscheme/mapping

      Expected Results

      The Rest API endpoint returns issue-type IDs that currently exist in the instance

      Actual Results

      Non-existent issue type IDs are returned in the above API responses

      Workaround

      Please contact Atlassian Support to assist in removing the non-existing issuetype entries.

            Assignee:
            Mudit Choraria
            Reporter:
            Bopanna
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: