Hi,
We still see this problem in "Jira Issue/Filter" macro when we use it in confluence, however the issue is not seen in "Filter Results" macro. Not sure why this happens.
Could you take a look at it please ?

Thanks
Venkatesh Prasad

Fix for multi user custom field will be released in 8.21.0:
https://jira.atlassian.com/browse/JRASERVER-32092

8 years for a "half-fix" - Wow!

Seriously guys? If you're going to do something, do it right or just don't do it at all! 

For us who thought that this would also apply to multi user picker fields, we should have known better. Instead, go to JRASERVER-32092 and put on your waiting hat for a few more years

Works fine for Singe user picker custom field but not for multi user picker custom field

I am awaiting for a new release

 It will be perfect if some works on this task and makes fixes! Guys, we need to have this fix

Is this issue really "In Progress" if it's been 1.5 years? It's in need of a status change and an official update from Atlassian.

14.11.2018 - Expect to hear an update on our progress in the coming weeks.

In Atlassian week takes 2 years, maybe

Is there any update on  this issue ? Which version of Jira Software is expected to get this problem solved ?

Hi Atlassian, is there any eta. on when this will be fixed? 

Please give us an update on this...

What's going on with this issue? It's a problem for our user experience.

Please give us an update on the status of this issue

I would also like an update for this request. Current "User picker" functionality is not very useful.

Thanks

Any update on when this enhancement will be implemented?  Last update was November 2018 saying work would be done on this soon.  Thanks!

@Atlassian - Please make sure this includes how the field displays in confluence - we currently have custom user picker fields and we have to use saved Jira filters instead of the Jira issues macro in Confluence in order to get the display name instead of the login ID.

If you use Scriptrunner, we've had great success with this custom built plugin: https://community.atlassian.com/t5/Agile-articles/Showing-the-values-of-user-picker-fields/ba-p/622613 

I need this as well!

I need it as well...This is not a good user experience. We need to see the first name and last name like Assignee, but instead it shows username.

We need it as well.

We would really need to have this bug fixed.

I'm sure it would be easier for us, the customers, to understand your side of things if SOMETHING would be communicated where are you standing with this? What is the issue / problem here?

 ¯_(ツ)_/¯

Full Names instead of user names. Please fix.

Would love to show Full Names instead of user names. Please fix.

Would love to get this fixed.
We use customfields (user picker) a lot and nobody reads the "User_ID" (3k people company).

It is really confusing (bad user experience).

I would love to have this fixed.

https://getsupport.atlassian.com/browse/GHS-105146

Hi David,

where we have to install this plugin, how to confifure it.

regards

Lingesh

I couldn't agree more with Anthony. Atlassian gives poor customer service companies a bad name. Even the tiniest improvements wanted by customers are utterly ignored. And while this workaround does improve things, it's not a solution. 

The workaround works, but Atlassian really does need to listen to their customers. This should be something very simple that they are able to fix. Something small and simple can make a lot of customers happy but Atlassian does not care.

Atlassian!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!  LISTEN TO YOUR CUSTOMERS.  THIS IS UNACCEPTABLE.

Jamie!  Once again, you rock!  It's not ideal, but at least users can see the user name now.

we used the solution given by Jamie and its working fine for us.[https://community.atlassian.com/t5/Agile-articles/Showing-the-values-of-user-picker-fields/ba-p/622613].

Has anybody else been able to find a workaround for this. Atlassian is apparently not looking at these requests. I am currently using the add on nFeed and created my own custom field which pulls form the Jira user database.

@Jamie:
thank´s for the tipp,

@Atlassian:
but a plugin can´t be the final resolution for this problem.

There is a new free plugin that should help with this - you can download from https://community.atlassian.com/t5/Agile-articles/Showing-the-values-of-user-picker-fields/ba-p/622613.

Please make this happen!

any plans to implement this?

Also still waiting (since 09.2016), and each comment is like spark of hope ...

My company is in need of this functionality as well.  Seems like it should be universal in how the data can be / is displayed.  

Any update here? Seems like a easy fix.

We have several user-picker fields defined in order to lay out the team involved in larger epics. Please provide an update on this issue!

• 19/Dec/2012 createt this issue
• 06/Dec/2013 changed the summary
• 31/Jul/2014 changed from improvement to suggestion
• 29/May/2015 changed from feature request to bug workflow
• 2016 nothing (break,leisure, holyday???)
• 2017 make attlassian great again and resolve this problem

What does it taker to get a response from Atlassian? It should be an easy fix, yet years later there's still no action. I don't get it. 

This is quite an old issue, is there any workaround please?

We're still looking for movement on this.

As a new user of this product, fairly quickly locating this issue I find the lack of any indication of movement on this item, plus the number of people who have made comments and votes on this issue somewhat concerning.

Surely there are security issues with having individuals userids being visible in these fields?

Honestly, this is a must-have. Yet, no activity on this issue whatsoever.

Can we please have an update on this issue?

Any workarounds or solutions on this issue? It has been open since 2012!!!!

This is also a must have for us. Any update from Atlassian?

Must have for us. The usernames used in our company are random strings of 3 letters (due to historical reasons). Not being able to see the selected user's full name is bad UX.

Any update on this? Otherwise I'm going to have to change everyones usernames which is massively not ideal!!

What is happening with this issue?

Same here. This issue was created in 2012 and we will still talk in 2022 about this feature request. #justatlassianthings

We have the same problem. In our large organizations the username not as useful as the Full Name in identifying people.

Same for me, this feature would improve the acceptance of our workflows

Arie Murdianto, That "answer" you left for Mike didn't help at all.
What behavior needs to be changed in the jira core code?
What do you mean "to generate the data in xml format?
This is a simple issue. Reporter & ReporterFullName and Assignee and AssigneeFullName are different referable fields. How does one get a User Picker field to display the Full Name "alias" when the data is referenced in a gadget, report, dashboard, or whereever?
And please be more specific than "you need to modify behavior of jira".