Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-72062

Using the auto complete for JQL search on a user populates the username value which can be a UUID

      Issue Summary

      Where performing a JQL search using a user field, selecting a value from the auto-complete options will populate username.

      In the case of newer users, for example those provisioned with SCIM this is a UUID and not human readable in a usable sence.

      Steps to Reproduce

      1. Provision a new user with SCIM.
      2. Assign an issue to the new user.
      3. Search for this user using JQL and type the display name of the user
         assignee = jira 
      4. Then select this user from the autocomplete pop-up.

      Expected Results

      The best result would be that the auto populated value would be either display name.

      Actual Results

      The username is populated which going forward will be a UUID.

      Notes

      This is related to the work being done to facilitate: Say goodbye to usernames in Atlassian Cloud

      Workaround

      To workaround this avoid using the auto-complete option and type the users display name or email address in quotes like

      assignee = "nero@jira.com"
      assignee = "Nero Battlebeard Wolfgang"

        1. image-2024-02-15-14-18-10-271.png
          image-2024-02-15-14-18-10-271.png
          317 kB
        2. image-2024-09-26-10-11-03-182.png
          image-2024-09-26-10-11-03-182.png
          499 kB
        3. screenshot-1.png
          screenshot-1.png
          34 kB
        4. screenshot-2.png
          screenshot-2.png
          317 kB
        5. Screenshot 2019-05-16 at 10.08.12.png
          Screenshot 2019-05-16 at 10.08.12.png
          17 kB
        6. Screenshot 2019-05-16 at 10.15.30.png
          Screenshot 2019-05-16 at 10.15.30.png
          32 kB
        7. screenshot-3.png
          screenshot-3.png
          480 kB
        8. screenshot-4.png
          screenshot-4.png
          379 kB

            [JRACLOUD-72062] Using the auto complete for JQL search on a user populates the username value which can be a UUID

            When you have the old search enabled, SOME screens show the new search regardless. In such screens, there is a button enigmatically called "Go to all issues" in the top right, next to "share" and "export issues" which allows you to go to the old search.

            The issue you just referenced is indeed the one that prevents us from using the new search. Thanks

            Alexandre Mikhalenkov added a comment - When you have the old search enabled, SOME screens show the new search regardless. In such screens, there is a button enigmatically called "Go to all issues" in the top right, next to "share" and "export issues" which allows you to go to the old search. The issue you just referenced is indeed the one that prevents us from using the new search. Thanks

            97239efeef31 

              

            Issue search "all issues" that we must use all the time because the new search for some reason does not show ALL labels, but only some of them... still unusable, shows UUIDs.

             

            Sorry I wasn't clear that you were referring to using the old search when you said "all issues". Can I double-check is this the label issue you were referring to?: JRACLOUD-83652 – New issue search results - Components/Labels/Fields with multiple values only show '+X' instead all values like the old issue search results.

            Anusha Rutnam added a comment - 97239efeef31      Issue search "all issues" that we must use all the time because the new search for some reason does not show ALL labels, but only some of them... still unusable, shows UUIDs.   Sorry I wasn't clear that you were referring to using the old search when you said "all issues". Can I double-check is this the label issue you were referring to?: JRACLOUD-83652 – New issue search results - Components/Labels/Fields with multiple values only show '+X' instead all values like the old issue search results.

            Thank you very much for providing the links to the related issues!

            I guess it is the old search I have issue in. I was under impression I enabled the new search because on some screens I do not have the choice any more, but yes, the screen there is an issue in is definitely the old search. As I said in my previous comment, I only use the old search because the new one does not show all labels, but just a short version like "Label One +5".

            Alexandre Mikhalenkov added a comment - Thank you very much for providing the links to the related issues! I guess it is the old search I have issue in. I was under impression I enabled the new search because on some screens I do not have the choice any more, but yes, the screen there is an issue in is definitely the old search. As I said in my previous comment, I only use the old search because the new one does not show all labels, but just a short version like "Label One +5".

            Hey 97239efeef31 this bug was closed because it is no longer reproducible in the new issue search navigator: 

             
            Other JQL fields (such as those that appear in swimlane and quick filter settings) are covered in separate tickets as different engineering teams own the different fields:

            JRACLOUD-83504 – On the Quick Filter settings page JQL should refer to a readable user information e.g. user name / email instead of user ID

            I've just created a new one for swimlanes: JSWCLOUD-27239 – On the swimlanes settings page JQL should refer to a readable user information e.g. user name / email instead of user ID 

             

            • Board filters are still unusable, idem
            • Issue search "all issues" that we must use all the time because the new search for some reason does not show ALL labels, but only some of them... still unusable, shows UUIDs.

             

            I can't reproduce this when using the new issue search - can you confirm you have it enabled?:

            Anusha Rutnam added a comment - Hey 97239efeef31 this bug was closed because it is no longer reproducible in the new issue search navigator:    Other JQL fields (such as those that appear in swimlane and quick filter settings) are covered in separate tickets as different engineering teams own the different fields: JRACLOUD-83504  –  On the Quick Filter settings page JQL should refer to a readable user information e.g. user name / email instead of user ID I've just created a new one for swimlanes: JSWCLOUD-27239 – On the swimlanes settings page JQL should refer to a readable user information e.g. user name / email instead of user ID     Board filters are still unusable, idem Issue search "all issues" that we must use all the time because the new search for some reason does not show ALL labels, but only some of them... still unusable, shows UUIDs.   I can't reproduce this when using the new issue search - can you confirm you have it enabled?:

            Sorry to report that almost nothing is solved.

            • Swimlane filters are still unusable as they show UUIDS
            • Board filters are still unusable, idem
            • Issue search "all issues" that we must use all the time because the new search for some reason does not show ALL labels, but only some of them... still unusable, shows UUIDs.

            I think it may be the same in other places, like quick filters etc., I did not perform the full QA of Jira fields.

            Not sure why this ticket was closed despite these issues being mentioned in several comments. Maybe, there is another issue (or ten) for this particular bug, but no link(s) were provided, either. I must say I have little hope at this point, four years later, but I thought I should leave at least a comment about it.

             

            Alexandre Mikhalenkov added a comment - Sorry to report that almost nothing is solved. Swimlane filters are still unusable as they show UUIDS Board filters are still unusable, idem Issue search "all issues" that we must use all the time because the new search for some reason does not show ALL labels, but only some of them... still unusable, shows UUIDs. I think it may be the same in other places, like quick filters etc., I did not perform the full QA of Jira fields. Not sure why this ticket was closed despite these issues being mentioned in several comments. Maybe, there is another issue (or ten) for this particular bug, but no link(s) were provided, either. I must say I have little hope at this point, four years later, but I thought I should leave at least a comment about it.  

            Atlassian Update - May 2024

            As per this comment I am closing this ticket.

            If you do not think this issue should have been closed, please add a comment here saying why and we can reopen it.

            Anusha Rutnam added a comment - Atlassian Update - May 2024 As per this comment I am closing this ticket. If you do not think this issue should have been closed, please add a comment here saying why and we can reopen it.

            Hey 298add8771bf I believe we would need a separate feature request for the different search input ("queues filter") you are referring to.

            I had a similar conversation here and created this feature request for the search input that appears in Jira Software projects' quick filter settings: JRACLOUD-83504On the Quick Filter settings page JQL should refer to a readable user information e.g. user name / email instead of user ID
            I am from the Jira Software (not Jira Service Management) support team so this is not my area of expertise, but the Jira Service Management Support team should be able to assist with creating such a ticket on your behalf.

            Anusha Rutnam added a comment - Hey 298add8771bf I believe we would need a separate feature request for the different search input ("queues filter") you are referring to. I had a similar conversation here and created this feature request for the search input that appears in Jira Software projects' quick filter settings: JRACLOUD-83504 – On the Quick Filter settings page JQL should refer to a readable user information e.g. user name / email instead of user ID I am from the Jira Software (not Jira Service Management) support team so this is not my area of expertise, but the Jira Service Management Support team should be able to assist with creating such a ticket on your behalf.

            Hi there,

            the new issue search's feature seem to only be available in the advanced issue search. I'd like to reference https://support.atlassian.com/requests/PCS-276542/

            To be precise, there are other places where this feature is not available yet. In my case it is Jira Service Management queues filter. My customer has several queue filters which involve specific users to exclude. At the moment the accountid is shown. Consider bringing this functionality to all places where JQL can be entered, e.g. JSM queues, JSW boards (quick-filters, colors,...) etc.

            Patrice (DEMICON) added a comment - Hi there, the new issue search's feature seem to only be available in the advanced issue search. I'd like to reference https://support.atlassian.com/requests/PCS-276542/ To be precise, there are other places where this feature is not available yet. In my case it is Jira Service Management queues filter. My customer has several queue filters which involve specific users to exclude. At the moment the accountid is shown. Consider bringing this functionality to all places where JQL can be entered, e.g. JSM queues, JSW boards (quick-filters, colors,...) etc.

            Anusha Rutnam added a comment - - edited

            Hi everyone, as of yesterday all users should be able to access the "new issue search experience."

            As the problem described in this ticket does not occur in the new issue navigator (see 15 February 2024 update in this ticket's Description), I'd like to tentatively suggest that this ticket can be closed but will wait a week before performing any actions.

            If you think that this ticket should remain open, please leave a comment stating why. Thank you!

            Anusha Rutnam added a comment - - edited Hi everyone, as of yesterday all users should be able to access the " new issue search experience ." As the problem described in this ticket does not occur in the new issue navigator (see 15 February 2024 update in this ticket's Description), I'd like to tentatively suggest that this ticket can be closed but will wait a week before performing any actions. If you think that this ticket should remain open, please leave a comment stating why. Thank you!

            Atlassian Update – 15 February 2024

            Hi everyone,

            The problem described in this ticket does not occur in the new issue navigator which we are aiming to roll out over the next few months. You can find more information here: JRACLOUD-74155Consolidated search for Jira Cloud

            You can test out this functionality by going to any company-managed project > Issues:

            Anusha Rutnam added a comment - Atlassian Update – 15 February 2024 Hi everyone, The problem described in this ticket does not occur in the new issue navigator which we are aiming to roll out over the next few months. You can find more information here: JRACLOUD-74155 – Consolidated search for Jira Cloud You can test out this functionality by going to any company-managed project > Issues:

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

                Created:
                Updated:
                Resolved: