Summary

      The assignee picker can show duplicated last user on the list, compounding on multiple clicks of the assignee field.

      Steps to Reproduce

      1. Create a Jira instance with 15 or more users
      2. Create a project with an issue in it, and assign the issue to one of the users
      3. Change the assignee to another user, and refresh the issue
      4. Click the assignee field, and scroll down the list

      Expected Results

      No users are duplicated.

      Actual Results

      Last user on the list will be duplicated in the list.

      Notes

      There are multiple requests to the <base-url>/rest/api/latest/user/assignable endpoint. The rest endpoint is hit when clicking the "down" arrow, and when scrolling to the bottom of the list.

      Workaround

      There is no workaround at this time.

          Form Name

            [JRASERVER-66060] Assignee picker shows last user twice

            ludong added a comment -

            Still in v9.4.5

            ludong added a comment - Still in v9.4.5

            Already fixed in 8.20.12 and 9.3.0

            Grzegorz Kuliński (Inactive) added a comment - Already fixed in 8.20.12 and 9.3.0

            papireddy added a comment -

            we are still facing this issue in 9.4.1,Please suggest if there is any workaround on this.

            papireddy added a comment - we are still facing this issue in 9.4.1,Please suggest if there is any workaround on this.

            IT IT added a comment -

            Still in v9.4.1

            IT IT added a comment - Still in v9.4.1

            Still having the same issue on 8.20.12...

            Jessie Chia added a comment - Still having the same issue on 8.20.12...

            Justin added a comment -

            We're still experiencing this issue in version v9.3.0

            Justin added a comment - We're still experiencing this issue in version v9.3.0

            d2f6a8c01472 e958f25c216d 4fb9694bc4b7 870304bfc0d7 This issue is about duplicated last user in Asignee Picker like on attached screenshot and it has been fixed. Please check Issue links in this ticket maybe one of them goes exactly with the client problem

            Karol Skwierawski added a comment - d2f6a8c01472 e958f25c216d 4fb9694bc4b7 870304bfc0d7 This issue is about duplicated last user in Asignee Picker like on attached screenshot and it has been fixed. Please check Issue links in this ticket maybe one of them goes exactly with the client problem

            There's no known workaround yet. If anyone finds one, please let us know on here as I don't feel Atlassian is going to fix this issue (they seem to think it's already fixed). It just sucks balls to not have anything we could try for affected customers.

            Peter Leitner [catworkx] added a comment - There's no known workaround yet. If anyone finds one, please let us know on here as I don't feel Atlassian is going to fix this issue (they seem to think it's already fixed). It just sucks balls to not have anything we could try for affected customers.

            Our client is experiencing this, is there a workaroun

            Noni Khutane added a comment - Our client is experiencing this, is there a workaroun

            Hi, Team!
            One of our clients too facing the same issue.
            The duplication of the users in the dropdown list of assignee picker.
            When can we expect this bug to be resolved?

            Thanks and regards
            Madhusudan

            Madhusudan Bhosale added a comment - Hi, Team! One of our clients too facing the same issue. The duplication of the users in the dropdown list of assignee picker. When can we expect this bug to be resolved? Thanks and regards Madhusudan

            We have the same scenario as Benjamin W with a recent upgrade to v8.20.13. A user can be located in more than one directory.

            Paul Gryfakis added a comment - We have the same scenario as Benjamin W with a recent upgrade to v8.20.13. A user can be located in more than one directory.

            Nayana

            we have updgraded from 8.20.11 to 8.20.13.
            We have first experienced the issue since upgrade from 8.20.3 to 8.20.7.

            We do have multiple AD Directories where 1 user can be located in multiple Directories.

            The screenshot above shows that only the last user is shown twice. For us, all the entries are shown twice. As I am not able to add a screenshot onto here in order to demonstrate.

            Regards, Benjamin

            Benjamin W. added a comment - Nayana we have updgraded from 8.20.11 to 8.20.13. We have first experienced the issue since upgrade from 8.20.3 to 8.20.7. We do have multiple AD Directories where 1 user can be located in multiple Directories. The screenshot above shows that only the last user is shown twice. For us, all the entries are shown twice. As I am not able to add a screenshot onto here in order to demonstrate. Regards, Benjamin

            NAYANA added a comment -

            Benjamin,

            Which version were you on previously?

            We are on 8.20.6 and haven't upgraded yet - we see this issue but strangely not for all users. There are some users who appear only once and others appear twice.

            Are we using multiple directories - NO - there is only one LDAP/AD which is our source of truth.

            I am curious if you are seeing this issue for all users and if upgrade did not help at all?

            NAYANA added a comment - Benjamin, Which version were you on previously? We are on 8.20.6 and haven't upgraded yet - we see this issue but strangely not for all users. There are some users who appear only once and others appear twice. Are we using multiple directories - NO - there is only one LDAP/AD which is our source of truth. I am curious if you are seeing this issue for all users and if upgrade did not help at all?

            We have updated Jira DC to 8.20.13 but we are still facing the issue.

            As 8.20.13 (which is latest LTS) includes 8.20.12 (which is the named fixed version) I would exped the issue to be fixed as well.

            Can anyone confirm wether it is fixed in 8.20.12?

            Benjamin W. added a comment - We have updated Jira DC to 8.20.13 but we are still facing the issue. As 8.20.13 (which is latest LTS) includes 8.20.12 (which is the named fixed version) I would exped the issue to be fixed as well. Can anyone confirm wether it is fixed in 8.20.12?

            Same here, also with 9.1.0

            Andreas Pohl added a comment - Same here, also with 9.1.0

            We have also this behavior after upgrading to 8.20.10

            Andreas Xanthos added a comment - We have also this behavior after upgrading to 8.20.10

            Leena Swar added a comment -

            We have upgraded to 8.20.10 Version still we are facing the same issue 

            Leena Swar added a comment - We have upgraded to 8.20.10 Version still we are facing the same issue 

            Topicus added a comment -

            Same here, v8.22.2 still affected and super annoying.

            Topicus added a comment - Same here, v8.22.2 still affected and super annoying.

            ipm added a comment - - edited

            We upgraded to 8.22.2 and got this issue as well.

            We have users from two different Active Directory Domains - only users from one Domain are shown twice, the others not.

            ipm added a comment - - edited We upgraded to 8.22.2 and got this issue as well. We have users from two different Active Directory Domains - only users from one Domain are shown twice, the others not.

            CP added a comment -

            We have also this behaviour after upgrading to 8.20.6

            CP added a comment - We have also this behaviour after upgrading to 8.20.6

            IT IT added a comment -

            Same behaviour here after 8.20.8 update

            IT IT added a comment - Same behaviour here after 8.20.8 update

            After upgrading to 8.20.8 the field "Assignee" and the mention function "@[name]" list the names of the users twice.

            eike.kowertz added a comment - After upgrading to 8.20.8 the field "Assignee" and the mention function "@ [name] " list the names of the users twice.

            We started having this issue after upgrading from 8.13.5 --> 8.20.8.

            juri.ahokas added a comment - We started having this issue after upgrading from 8.13.5 --> 8.20.8.

            Updated from 8.20.3 to 8.20.7 and since then also experience this issue.

            Desktop/Browser only assignee is affected.
            Mobile App for iOS all userpicker fields are affected.

            We have users from three different Active Directory Domains - only users from one Domain are shown twice, the others not.

            Benjamin W. added a comment - Updated from 8.20.3 to 8.20.7 and since then also experience this issue. Desktop/Browser only assignee is affected. Mobile App for iOS all userpicker fields are affected. We have users from three different Active Directory Domains - only users from one Domain are shown twice, the others not.

            We have this issue after updating Jira Server 8.20.2 to 8.20.7.

            Stefan Junge added a comment - We have this issue after updating Jira Server 8.20.2 to 8.20.7.

            Experiencing the issue (it was reported in this ticket as well https://jira.atlassian.com/browse/JRASERVER-44113) Please resolve this already

            Antreas Solou added a comment - Experiencing the issue (it was reported in this ticket as well https://jira.atlassian.com/browse/JRASERVER-44113 ) Please resolve this already

            Sys Admin added a comment -

            In JRASERVER-67711 there are 2 possible workarounds for solving this until Atlassian fixes the issue.

            Sys Admin added a comment - In  JRASERVER-67711 there are 2 possible workarounds for solving this until Atlassian fixes the issue.

            Hentsu added a comment -

            Hi,

             

            We are experiencing this in Jira 8.4.1, core and software only,  no service desk. Issue came out of nowhere a few days ago.

            Also we get this no matter where the user picker is called from, despite past related ticket stating that its fixed and any new problems are an edge case with inline user picker https://jira.atlassian.com/browse/JRASERVER-44113

             

            can confirm that F12 network monitor shows multiple calls to BASE_URL/rest/api/latest/user/assignable/search?=JQL_QUERY

             

            Thanks

            Hentsu added a comment - Hi,   We are experiencing this in Jira 8.4.1, core and software only,  no service desk. Issue came out of nowhere a few days ago. Also we get this no matter where the user picker is called from, despite past related ticket stating that its fixed and any new problems are an edge case with inline user picker  https://jira.atlassian.com/browse/JRASERVER-44113   can confirm that F12 network monitor shows multiple calls to BASE_URL/rest/api/latest/user/assignable/search?=JQL_QUERY   Thanks

            Hi,

            I have the same problem (when there are two User Directories from AD and the user belongs to both and has the same username).

            Sergey Karaev (Aplana) added a comment - Hi, I have the same problem (when there are two User Directories from AD and the user belongs to both and has the same username).

            Hi, Team

            We are experiencing this issue on some of our users while others are not. Any clue?

            Enkhbayar Yura added a comment - Hi, Team We are experiencing this issue on some of our users while others are not. Any clue?

            Hi Atlassian Team,

            We are also facing this issue in our production environment. Please suggest how to fix or deal with this issue. 

            Thanks,

            Anoop

            AnoopTripathi added a comment - Hi Atlassian Team, We are also facing this issue in our production environment. Please suggest how to fix or deal with this issue.  Thanks, Anoop

            I have the same as @Peter Heitbrock mentioned in his comment of Sept 7th 2018. I have a duplicate at the end of the assignee user list. We use Jira 7.11.0.

            Sandra Meessen added a comment - I have the same as @Peter Heitbrock mentioned in his comment of Sept 7th 2018. I have a duplicate at the end of the assignee user list. We use Jira 7.11.0.

            Thank you for pointing that out bbridges. I have updated this request to reflect the latest versions affected mentioned as well as linking this request to JRASERVER-44113.

            Best regards,
            René Chiquete - JAC Champion.

            Rene C. [Atlassian Support] added a comment - Thank you for pointing that out bbridges . I have updated this request to reflect the latest versions affected mentioned as well as linking this request to JRASERVER-44113 . Best regards, René Chiquete - JAC Champion.

            It seems like this is duplicate of a previously reported issue (JRASERVER-44113) which was reportedly fixed, but then apparently broken again.

            Bryan Bridges added a comment - It seems like this is duplicate of a previously reported issue ( JRASERVER-44113 ) which was reportedly fixed, but then apparently broken again.

            llagos added a comment - - edited

            Same issue on Jira v7.6.8 and JIRA v7.5.3 (Service Desk v3.9.8 AND v3.9.4)

            Duplicates appear when you click on the down arrow of the scrolling bar.

            llagos added a comment - - edited Same issue on Jira v7.6.8 and JIRA v7.5.3 (Service Desk v3.9.8 AND v3.9.4) Duplicates appear when you click on the down arrow of the scrolling bar.

            We have the same issue with 7.7.2. We have  at least 2 duplicate - both are located at the end of the user names (alphabetically).

            Peter Heitbrock added a comment - We have the same issue with 7.7.2. We have  at least 2 duplicate - both are located at the end of the user names (alphabetically).

            Just upgraded test from 7.3.4 to 7.9.2 and ouch.  How is this considered minor?  Was working in earlier versions and now it looks really awful when the list duplicates itself.

            Susan Hauth [Jira Queen] added a comment - Just upgraded test from 7.3.4 to 7.9.2 and ouch.  How is this considered minor?  Was working in earlier versions and now it looks really awful when the list duplicates itself.

            Kishore Kumar K added a comment - - edited

            ..

            Kishore Kumar K added a comment - - edited ..

              4e432536cf93 Karol Skwierawski
              mkwidzinski Maciej Kwidziński (Inactive)
              Affected customers:
              123 This affects my team
              Watchers:
              113 Start watching this issue

                Created:
                Updated:
                Resolved: