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

Workflow import should warn if the status does not exist

XMLWordPrintable

      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 made changes -
            Labels New: jracloud-stale-triage
            Dylan made changes -
            Resolution New: Obsolete [ 11 ]
            Status Original: Gathering Impact [ 12072 ] New: Closed [ 6 ]
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1847294 ] New: JAC Bug Workflow v3 [ 3354353 ]
            Status Original: Verified [ 10005 ] New: Gathering Impact [ 12072 ]
            Eric S (Inactive) made changes -
            Component/s New: Project and System Administration - Workflows and statuses [ 53194 ]
            Component/s Original: Project Administration - Workflows [ 46562 ]
            jonah (Inactive) made changes -
            Description Original: 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.             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This bug report is for *JIRA Cloud*. Using *JIRA Server*? [See the corresponding bug report|http://jira.atlassian.com/browse/JRASERVER-27924].
              {panel}

            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.
            jonah (Inactive) made changes -
            Link New: This issue is related to JRASERVER-27924 [ JRASERVER-27924 ]
            vkharisma made changes -
            Project Import New: Sat Apr 01 19:36:47 UTC 2017 [ 1491075407146 ]
            Michael Tokar made changes -
            Eric S (Inactive) made changes -
            jonah (Inactive) made changes -

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

                Created:
                Updated:
                Resolved: