Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JRACLOUD-65785

Failure to import from BitBucket when mapped issue types are not present in destination project's 'Issue Type Scheme'

    XMLWordPrintable

Details

    Description

      A bug is happening on import of projects from Bitbucket to JIRA. When issues are imported to a JIRA project, their issue types are requested, as the image below shows:

      The available issue types are not the ones in the project’s ‘Issue Type Scheme’ and when selected an issue type that is not one of the types available for the project, an error occurs.
      This is the error

      It reads ‘Error importing issue ExternalIssue

      {externalId=1, summary=Test issue, issueType=1}

      When checking the logs, the follow stacktrace is present for the error:

      ERROR - Error importing issue ExternalIssue{externalId=2, summary=Mode command text moves when mouse is held down, issueType=1}
      com.atlassian.jira.plugins.importer.external.ExternalException: Unable to create or update issue: ExternalIssue{externalId=2, summary=Mode command text moves when mouse is held down, issueType=1}
      	at com.atlassian.jira.plugins.importer.imports.importer.impl.DefaultJiraDataImporter.createIssue(DefaultJiraDataImporter.java:903)
      	at com.atlassian.jira.plugins.importer.imports.importer.impl.DefaultJiraDataImporter.importIssues(DefaultJiraDataImporter.java:764)
      	at com.atlassian.jira.plugins.importer.imports.importer.impl.DefaultJiraDataImporter.doImport(DefaultJiraDataImporter.java:390)
      	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      	at java.lang.reflect.Method.invoke(Method.java:597)
      	at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
      	at org.springframework.osgi.service.importer.support.internal.aop.ServiceInvoker.doInvoke(ServiceInvoker.java:58)
      	at org.springframework.osgi.service.importer.support.internal.aop.ServiceInvoker.invoke(ServiceInvoker.java:62)
      	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
      	at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
      	at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
      	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
      	at org.springframework.osgi.service.util.internal.aop.ServiceTCCLInterceptor.invokeUnprivileged(ServiceTCCLInterceptor.java:56)
      ...
      

      Steps to reproduce

      • Create a project in JIRA that does not contain all issue types
      • Create a project in BitBucket and create issues
      • Import the project in Bitbucket to the project in JIRA
      • Map some issue types (with existent issues in BitBucket) in the project to types that are not mapped to the project
      • Begin import
      • The error will occur

      Workarounds

      • Check carefully the types to make sure no type is mapped to unmapped types in the project

      Attachments

        Issue Links

          Activity

            People

              ohookins@atlassian.com Oliver Hookins (Inactive)
              jsilveira Jaime S
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: