IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-27920

Workflow import should warn if the status does not exist

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • 6.0
    • None
    • None
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

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

      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.

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Jira Data Center'
            1. Jira Data Center
            2. JRASERVER-27920

            Workflow import should warn if the status does not exist

            XMLWordPrintable

              • Icon: Suggestion Suggestion
              • Resolution: Fixed
              • 6.0
              • None
              • None
              • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

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

                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.

                        Unassigned Unassigned
                        mmangier Malik Mangier (Inactive)
                        Votes:
                        1 Vote for this issue
                        Watchers:
                        4 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            Unassigned Unassigned
                            mmangier Malik Mangier (Inactive)
                            Votes:
                            1 Vote for this issue
                            Watchers:
                            4 Start watching this issue

                              Created:
                              Updated:
                              Resolved: