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

The xml for version picker customfield provides the version id instead of the version name

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Low
    • 7.12.0, 8.0.0
    • None
    • None
    • None
    • 2
    • Severity 3 - Minor
    • 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

    Description

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

      xml-version.vm used for xml output of version picker customfields provides the version's id instead of the version's name. This results in data that has little meaning to the end user when consuming rss or the jiraissues macro in confluence

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              4d109d63b4aa Justin Shapiro
              Votes:
              2 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: