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

Workflow import should warn if the status does not exist

      NOTE: This bug report is for JIRA Cloud. Using JIRA Server? See the corresponding bug report.

      If you import an XML workflow that came from another instance, without making sure that all the issue status existed in the new instance, there will be probems:

      http://confluence.atlassian.com/display/JIRAKB/NullPointerException+after+importing+workflow+XML

      It would be better if the import function would warn with an error message saying that the XML import was referencing unexisting objects.

            [JRACLOUD-27924] Workflow import should warn if the status does not exist

            Dylan added a comment -

            Hi all, we're closing this issue because there have been no reports of it re-occurring in the last 2 years. Please feel free to comment or contact support if this is still impacting you and we will be happy to re-open and assess.

            Cheers,
            Atlassian Support

            Dylan added a comment - Hi all, we're closing this issue because there have been no reports of it re-occurring in the last 2 years. Please feel free to comment or contact support if this is still impacting you and we will be happy to re-open and assess. Cheers, Atlassian Support

              Unassigned Unassigned
              mmangier Malik Mangier (Inactive)
              Affected customers:
              1 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: