Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-31977

xml view of custom field of multiversion picker type display version ID instead of version text

XMLWordPrintable

    • 4.02
    • 14
    • Severity 2 - Major
    • 232
    • Hide
      Atlassian Update – 21 December 2018

      Dear Jira users,

      We’re glad to announce that this issue will be addressed in our upcoming 8.0 release.

      You can find more details about our 8.0 beta release here — https://community.developer.atlassian.com/t/beta-for-jira-8-0-is-up-for-grabs/25588

      Looking forward to your feedback!

      Kind regards,
      Syed Masood
      Product Manager, Jira Server and Data Center

      Show
      Atlassian Update – 21 December 2018 Dear Jira users, We’re glad to announce that this issue will be addressed in our upcoming 8.0 release. You can find more details about our 8.0 beta release here — https://community.developer.atlassian.com/t/beta-for-jira-8-0-is-up-for-grabs/25588 Looking forward to your feedback! Kind regards, Syed Masood Product Manager, Jira Server and Data Center

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

      <customfield id="customfield_10930" key="com.atlassian.jira.plugin.system.customfieldtypes:multiversion">
      <customfieldname>Target Release</customfieldname>
      <customfieldvalues>
      <customfieldvalue>36029</customfieldvalue>
      </customfieldvalues>
      </customfield>

      As a result, the issue macro display result of Target Release as 36029 instead of 13.04

      Steps to Reproduce

      • Create a custom field in JIRA that deals with versions (either 'Version Picker' or 'Multi Version Picker')
      • Open any ticket and try to add these versions and put the values
      • Use the JIRA XML API to get the value of these custom fields
      • Expectation to see the values of these versions
      • Actual, we only see the IDs of these versions

      Resolution

      • This issue is resolved out of the box in Jira 8.0.0
      • For Jira 7.13.x and 7.12.0, the dark feature outlined below will resolve the problem:
        1. Navigate to https://<JiraBaseURL>/secure/admin/SiteDarkFeatures!default.jspa
        2. Next to Enable dark feature, paste: 
          com.atlassian.jira.plugin.export.xml.unified.enabled

          and click Add

        3. Verify that the Jira Issue/Filter shows the correct result

        1. xml-issue-7.12.1.xml
          3 kB
        2. Screen Shot 2016-07-20 at 1.22.33 AM.png
          Screen Shot 2016-07-20 at 1.22.33 AM.png
          266 kB
        3. Bildschirmfoto 2017-07-24 um 13.52.16.png
          Bildschirmfoto 2017-07-24 um 13.52.16.png
          29 kB
        4. 2017-07-18 11_41_45-Clipboard.png
          2017-07-18 11_41_45-Clipboard.png
          36 kB

              psuwala ΞΔ (Inactive)
              539fc397a359 Anthony King
              Votes:
              56 Vote for this issue
              Watchers:
              63 Start watching this issue

                Created:
                Updated:
                Resolved: