Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-68162

Adding a Jira filter to a Confluence page which includes a customer Picker field from Jira in the view, displays the Jira username value instead of the display name

      Issue Summary

      If a Jira filter macros is added to the page and a custom single user picker field from Jira is included in the results display, this returns the users username value instead of their display name like with the reporter and assignee fields.

      Environment

      Confluence Cloud
      TinyMC & Fabric editors

      Steps to Reproduce

      1. Create a Jira and Confluence cloud site.
      2. In Jira create a customer single user picker field and add this to required screens and scopes.
      3. In Jira create a test issue and populate the custom user picker field with a user.
      4. Create a page in confluence.
      5. Add a Jira filter macro to the Confluence page.
      6. Include the customer user picker field in the displayed results in the Jira macro.
      7. Publish the page

      Expected Results

      The value in the custom user picker field within the Jira macro should return the display name for the user.

      Actual Results

      The value in the custom user picker field within the Jira macro is the username

      Notes

      This is especially problematic for SCIM provisioned users as they are issues a UUID as the username.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            [CONFCLOUD-68162] Adding a Jira filter to a Confluence page which includes a customer Picker field from Jira in the view, displays the Jira username value instead of the display name

            Atlassian Update - October 7, 2021

            Hi everyone,

            Thank you for previously raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Confluence users.

            As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.

            Thank you again for providing valuable feedback to our team!

            Matthew Hunter added a comment - Atlassian Update - October 7, 2021 Hi everyone, Thank you for previously raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Confluence users. As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know. Thank you again for providing valuable feedback to our team!

            Hi Team,

            Could you please provide the latest update on this issue.

            Regards

            Dhananjay M.Mukhedkar

            Dhananjay Mukhedkar added a comment - Hi Team, Could you please provide the latest update on this issue. Regards Dhananjay M.Mukhedkar

              Unassigned Unassigned
              nwolfgang Battlebeard (Inactive)
              Affected customers:
              10 This affects my team
              Watchers:
              18 Start watching this issue

                Created:
                Updated:
                Resolved: