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

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.

Following ticket for ETA on this fix

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?

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

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

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?

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

#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

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

We think that there is the following method if you only solve this problem.

Workaround:

1. Editing a xml-version.vm file
   (jira-application-dir)/atlassian-jira/WEB-INF/classes/templates/plugins/fields/xml/xml-version.vm

   #disable_html_escaping()
   #if ($value)
     #foreach ($singleValue in $value)
   <customfieldvalue>$xmlutils.escape($!singleValue.name)</customfieldvalue>
     #end
   #end
   

2. JIRA Service Resart
3. Confluence Service Restart (Optional)

We do not know about adverse effects of workaround.
We really need to resolve this issue.

Any update on this?