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

Display Full Name instead of username in User Picker Custom Field

    • 108
    • 20
    • Hide
      Atlassian Update – 9 July 2020

      Hi everyone,

      Thank you for your votes and comments on this suggestion.

      We would like to inform you that this suggestion will be addressed in the upcoming Jira Server and Data Center version 8.12.0 release.
      User picker type custom fields will be consistent with the system fields of the same type in Jira Server. The custom fields will display the full name and avatar, like the Assignee field does now, for example.

      Grażyna Kaszkur
      Product manager, Jira Server and Data Center

      Show
      Atlassian Update – 9 July 2020 Hi everyone, Thank you for your votes and comments on this suggestion. We would like to inform you that this suggestion will be addressed in the upcoming Jira Server and Data Center version 8.12.0 release. User picker type custom fields will be consistent with the system fields of the same type in Jira Server. The custom fields will display the full name and avatar, like the Assignee field does now, for example. Grażyna Kaszkur Product manager, Jira Server and Data Center
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

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

      Currently when you add a Custom Field User Picker to your screen and add a user to the value of the field, it will display the username, and not the Full Name like what is displayed for the Reporter field for example.

      Expected that there would be some unity between what is displayed in the field value on transition screens. See screenshot.

            [JRASERVER-31023] Display Full Name instead of username in User Picker Custom Field

            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

            venkateshprasad added a comment - 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

            Szymon Korytnicki (Inactive) added a comment - Fix for multi user custom field will be released in 8.21.0: https://jira.atlassian.com/browse/JRASERVER-32092

            Manuel added a comment -

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

            Manuel added a comment - 8 years for a "half-fix" - Wow!

            David Sumlin added a comment - - edited

            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

            David Sumlin added a comment - - edited 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

            Anilkumar B added a comment - Works fine for Singe user picker custom field but not for multi user picker custom field

            I am awaiting for a new release

            Alina Basenko added a comment - I am awaiting for a new release

            Kasturee added a comment -

            This must be some hectic solution that you are implementing that takes over 2 years to develop. Please, please, please can you complete this task or provide us with feedback. This is ridiculous

            Kasturee added a comment - This must be some hectic solution that you are implementing that takes over 2 years to develop. Please, please, please can you complete this task or provide us with feedback. This is ridiculous

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

            Alina Basenko added a comment -  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.

            Todd Thomas added a comment - 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

            Richard Bariny (Richardb953) added a comment - 14.11.2018 - Expect to hear an update on our progress in the coming weeks. In Atlassian week takes 2 years, maybe

              292ec441c8da Szymon Korytnicki (Inactive)
              pkirkeby Pelle Kirkeby (Inactive)
              Votes:
              311 Vote for this issue
              Watchers:
              218 Start watching this issue

                Created:
                Updated:
                Resolved: