• 2
    • 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.

      Importing data from JSON does not provide much detail about the requirements when importing from JSON for setting the various *Version fields.

      The JSON File Example has these correctly entered but the documentation doesn't explain clearly that in order to be able to an Issue and specify, for example, a fixVersion, the desired fixVersion needs to be defined in the JSON file. If the Version is already in JIRA, but not specified in the JSON under projects, this will be logged during import:

      Version does not exist for project
      

      Note also that this doesn't appear to affect custom fields using the Version picker types.

      Example, we need to define versions in json even if they already exist in Jira:

            "versions": [
                {
                    "name": "version_1"
                }
            ],
      

            [JRASERVER-62509] Add information about Versions for JSON importer

            There are no comments yet on this issue.

              wthompson Wazza
              rstadler@atlassian.com Russell Stadler (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: