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

Project import cant bring in data that is logically equaivalent

    XMLWordPrintable

Details

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

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

      Each version of JIRa has a different built number (by design)

      However project restricts itself to data on the exact same build number.

      So imagine a XML exported on 3.13.1. This data cannot be imported into 3.13.4, even though there are no upgrades anc changes to the data logically.

      The reason it does this is that it naively assumes that different build numbers means the upgrade tasks need to be run and the configuration of the data needs to be transformed.

      The improvement would be for project import to check ask the upgrade system if there are any upgrade tasks and if the answer is 0, then allow the import.

      So you would be able to move from 3.13.x to 3.13.x+n but not 4.x for example. This is a big improvement in my book.

      Attachments

        Issue Links

          is related to

          Suggestion - JRASERVER-18143 Project import cant bring in data that is logically equaivalent

          • Closed

          Activity

            People

              Unassigned Unassigned
              bbaker ɹǝʞɐq pɐɹq
              Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: