-
Bug
-
Resolution: Fixed
-
Highest
-
5.6.3, 6.3.2, 6.4.2, 6.12.2, 6.14.1, 6.13.4, 6.13.6, 6.13.8, 6.15.7, 7.4.4, 7.4.11, 7.13.0, 7.13.2, 7.13.5, 7.13.9, 7.14.0, 7.19.16, 7.19.17
-
35
-
Severity 3 - Minor
-
111
-
This fix relies on changes to both Confluence and Jira to function. As a result, both Confluence 8.4.0 and later, and Jira 9.9.0 and later will be required for this fix. Using the newer version of Confluence with an older version of Jira will continue to function as described below.
Steps to reproduce - JIRA 6.3.1-
- Create a project in JIRA and create custom field with User Picker.
- Set the application links.
- Go to Confluence and insert the XML URL.
- Be sure you specify the custom field when you're adding it to Confluence.
What you expect to see:
- See the Display name
What do you see:
- See the username
Information
tested in Jira 8.5.3
When the HTTP Dump Log is enabled in Jira during the request of Jira Issue Macro, we can see the below information coming from Jira:
<item>
<link>http://localhost:8853/j853/browse/MST-1</link>
<key id="10000">MST-1</key>
<summary>Do this</summary>
<type id="10000" iconUrl="http://localhost:8853/j853/secure/viewavatar?size=xsmall&avatarId=10318&avatarType=issuetype">Task</type>
<priority id="3" iconUrl="http://localhost:8853/j853/images/icons/priorities/medium.svg">Medium</priority>
<status id="10000" iconUrl="http://localhost:8853/j853/images/icons/status_generic.gif" description="">To Do</status>
<statusCategory id="2" key="new" colorName="blue-gray"/>
<resolution id="-1">Unresolved</resolution>
<assignee username="-1">Unassigned</assignee>
<reporter username="admin">The Mighty Administrator</reporter>
<created>Wed, 21 Apr 2021 12:15:48 +1000</created>
<updated>Fri, 14 May 2021 15:34:44 +1000</updated>
<due></due>
<customfields>
<customfield id="customfield_10207" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
<customfieldname>Development</customfieldname>
<customfieldvalues>
</customfieldvalues>
</customfield>
<customfield id="customfield_10102" key="com.atlassian.jira.plugin.system.customfieldtypes:userpicker">
<customfieldname>Pick Someone</customfieldname>
<customfieldvalues>
<customfieldvalue>caliburn</customfieldvalue>
</customfieldvalues>
</customfield>
</customfields>
</item>
Here, we can see that Jira is returning both Username and Display Name for the reporter field. Meanwhile, for the userpicker field only Username is returned
| Jira Field | Username | Display Name |
|---|---|---|
| reporter | admin | The Mighty Administrator |
| customfieldtypes:userpicker | caliburn |  |
This issue is likely caused by JRASERVER-20361 from the Jira end
Additional information:
This issue also observed with Jira cloud and Confluence server integration.
- When using Jira issue macro on Confluence page to fetch issue which contains custom Field user picker (multiple-users) it shows id instead if name however Jira cloud shows name.
- Jira Cloud:
- Confluence server:
- duplicates
-
CONFSERVER-18505 jiraissues macro could be improved to present full user names for user picker fields
- Gathering Interest
- is caused by
-
- Closed
- mentioned in
-
![[Confluence] Page](/images/icons/generic_link_16.png "[Confluence] Page")
Page
No Confluence page found with the given URL.
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
-
-
-
-
-
[CONFSERVER-35256] Custom Field user-picker should render display name within JIRA issue macro.
Still facing this problem in Confluence Server 8.5.5 and Jira 9.4.15
A fix for this issue is available in Confluence Server and Data Center 8.4.0.
Upgrade now or check out the Release Notes to see what other issues are resolved.
Hi All,
A quick update on this one.
As noted in the description, the root cause of this issue is the limitation of a Jira API which is tracked at JRASERVER-20361: XML view for filters containing user picker fields should return both userid and user full name.
Having spoken to our colleagues in the Jira team, they're looking into tackling this issue soon, so for the time being this issue is on hold. Once the Jira team have been able to tackle the issue on their end, we'll make the improvement on ours.
One thing to note here, this improvement will require updating both Jira and Confluence to get the fix.
I'll provide an update once we have more to share.
Thanks,
James Ponting
Engineering Manager - Confluence Data Center
Hi, I'd like to check any release plan for this issue? Multiple SSGA teammates had reported this issue and need an ETA. Thank you!
Facing the same issue to me in Confluence 7.13.5 with Jira 8.13.10. 
New year new luck new version (7.13) same problem.
For A similar issue with Epic Links CONFSERVER-43561 it tooks ONLY 
5 and a half years to resolve.
Come on Atlassian, try to fix bugs with the same performance as your license price increase rate
Hello Atlassian Team,
I would also added my vote to this issue for the name picker field to render name within Jira Issue macro.
Looking forward to the updates.
Thank you.
MR
Hello b653b26886d0,
As mentioned in the Note at the top of the bug description, the fix relies on both Confluence and Jira. Your Confluence version is matching with that but in order to fix to work as expected, your Jira should be upgraded to 9.9.0 or higher.
Hope this helps.
Kind regards,
Basar Beykoz