Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-32610

JIRA Issue Macro shows the ID instead of the value

XMLWordPrintable

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

      Summary of Bug

      When using the JIRA Issue Macro, for custom fields that deals with Versions, the ID of the value will be shown instead of the value itself

      Steps to Reproduce

      1. Create a custom field in JIRA that deals with versions(either 'Version Picker' or 'Multi Version Picker')
      2. Configure an applink between JIRA and Confluence, and then try using the JIRA Issue Macro to show the version fields
      3. The ID will be shown instead of the value

      This is the proper value :

      This is the result shown in the macro :

      Additional Info

      • This seems to only occur with custom fields, and does not affect system fields (Fix Version/s, for example)
      • Tested with Confluence 5.4.1, JIRA 6.1

        1. Screen Shot 2015-12-09 at 11.23.14 AM.png
          Screen Shot 2015-12-09 at 11.23.14 AM.png
          104 kB
        2. version picker.png
          version picker.png
          21 kB
        3. version value.png
          version value.png
          9 kB

            [CONFSERVER-32610] JIRA Issue Macro shows the ID instead of the value

            Brian Jarvis added a comment -

            add another company waiting for a fix on this

            Brian Jarvis added a comment - add another company waiting for a fix on this

            Minh Tran added a comment -

            Dear All,

            Thanks for raising your concerns and feedbacks for the bug. This bug sounds to appear from the JIRA side
            I just want to update you that we are tracking the reported problem of JIRA here https://jira.atlassian.com/browse/JRA-31977

            Thanks,
            Minh Tran
            Confluence BugMaster

            Minh Tran added a comment - Dear All, Thanks for raising your concerns and feedbacks for the bug. This bug sounds to appear from the JIRA side I just want to update you that we are tracking the reported problem of JIRA here https://jira.atlassian.com/browse/JRA-31977 Thanks, Minh Tran Confluence BugMaster

            Imesha Perera added a comment -

            This exists in Confluence 5.10.7 (with Integrated JIRA 7.1.9).

            This is affecting to custom fields that deals with *project pickers *as well.

            Imesha Perera added a comment - This exists in Confluence 5.10.7 (with Integrated JIRA 7.1.9). This is affecting to custom fields that deals with *project pickers *as well.

            Accounts Payable added a comment -

            Following ticket for ETA on this fix

            Accounts Payable added a comment - Following ticket for ETA on this fix

            Brad Nguyen added a comment - - edited

            This does not work for version 5.9.1. Would really appreciate if this issue can get fix soon. Do you have an ETA on when this would get fix for confluence?

            Brad Nguyen added a comment - - edited This does not work for version 5.9.1. Would really appreciate if this issue can get fix soon. Do you have an ETA on when this would get fix for confluence?

            Nayanajith Chandradasa added a comment -

            Please update affects version/s to have 5.8.8 of confluence as well

            Nayanajith Chandradasa added a comment - Please update affects version/s to have 5.8.8 of confluence as well

            Nayanajith Chandradasa added a comment -

            Could you please provide us a rough timeline on when this fix will be implemented?

            Nayanajith Chandradasa added a comment - Could you please provide us a rough timeline on when this fix will be implemented?

            Chuck Vanderwist added a comment -

            This really stinks that we can't have continuity between 2 atlassian applications when it comes to the way that fields are displayed.
            It's really difficult and confusing when both applications share the same user base (directory server), but we can't resolve a User's name from a UserID field for display in the confluence page?

            Chuck Vanderwist added a comment - This really stinks that we can't have continuity between 2 atlassian applications when it comes to the way that fields are displayed. It's really difficult and confusing when both applications share the same user base (directory server), but we can't resolve a User's name from a UserID field for display in the confluence page?

            Michele Sacchetti added a comment -

            the xmlutil escape didn't work to me, it shown it as a string on confluence macro,
            but this version of the same file worked fine for both the custom field version and the original version fields

            (jira-application-dir)/atlassian-jira/WEB-INF/classes/templates/plugins/fields/xml/xml-version.vm
            #disable_html_escaping()
#if ($value)
    #foreach ($singleValue in $value)
#if ($singleValue.name)
<customfieldvalue>$singleValue.name</customfieldvalue>
#else
<customfieldvalue>$!singleValue.id</customfieldvalue>
#end
    #end
#end

            restart of both Jira and Confluence required

            Michele Sacchetti added a comment - the xmlutil escape didn't work to me, it shown it as a string on confluence macro, but this version of the same file worked fine for both the custom field version and the original version fields (jira-application-dir)/atlassian-jira/WEB-INF/classes/templates/plugins/fields/xml/xml-version.vm #disable_html_escaping() # if ($value) #foreach ($singleValue in $value) # if ($singleValue.name) <customfieldvalue>$singleValue.name</customfieldvalue> # else <customfieldvalue>$!singleValue.id</customfieldvalue> #end #end #end restart of both Jira and Confluence required

            Andre Lehmann added a comment -

            We have the same behaviour on our instances.
            Confluence 5.7.1 and Jira 6.4.7.

            Its not really a blocker but its not really nice on all our Confluence-reports

            Andre Lehmann added a comment - We have the same behaviour on our instances. Confluence 5.7.1 and Jira 6.4.7. Its not really a blocker but its not really nice on all our Confluence-reports

              thunguyen Thuan Nguyen
              jtye Joe Wai Tye (Inactive)
              Affected customers:
              32 This affects my team
              Watchers:
              50 Start watching this issue

                Created:
                Updated:
                Resolved: