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

Scrolling down list of users in the "Assign Issue" dialog results in duplicate users appearing (Edge case)

XMLWordPrintable

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

      Summary

      This is the edge case of JRA-44113.
      JRA-44113 has already been closed but the problem sill occurred in the following scenario.

      Steps to Reproduce

      1. Create 15-20 users, ensure all of them are able to be assigned issues (you need enough users to cause the user list in the Assign Issue dialog to have to scroll).
      2. Assign 2-3 users you created in Step 1 to some tickets to make them appear in Suggestion section in the assignee list. (Please check this KB to understand how the suggestions are calculated.)
        Please make sure the 2-3 users are not in the end of All Users list.
      3. Click Assign, then hit the dropdown arrow in the Assignee field.
      4. Scroll down (using the keyboard or trackpad/mouse, it doesn't matter) to the bottom of the list.

      Expected Results

      You reach the bottom of the user list and there's no duplicates.

      Actual Results

      There are some duplicate in the user list.

      Notes

      • This isn't browser-specific (I can replicate it in Firefox, Chrome, and Safari)
      • This problem is also reproduced when creating an issue

      Workaround

      Currently there's no workaround, but this issue is purely cosmetic.

        1. screenshot-1.png
          screenshot-1.png
          206 kB

            [JRACLOUD-63554] Scrolling down list of users in the "Assign Issue" dialog results in duplicate users appearing (Edge case)

            Dylan made changes -
            Resolution New: Won't Fix [ 2 ]
            Status Original: Gathering Impact [ 12072 ] New: Closed [ 6 ]

            Dylan added a comment -

            Due to an extended period of inactivity and low interest this bug has been auto-closed. If you’re still experiencing this issue, please comment and we’ll re-open to triage.

            Cheers,

            Dylan - Service Enablement @ Atlassian

            Dylan added a comment - Due to an extended period of inactivity and low interest this bug has been auto-closed. If you’re still experiencing this issue, please comment and we’ll re-open to triage. Cheers, Dylan - Service Enablement @ Atlassian
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1824253 ] New: JAC Bug Workflow v3 [ 3360164 ]
            Status Original: Verified [ 10005 ] New: Gathering Impact [ 12072 ]
            Eric S (Inactive) made changes -
            Component/s New: Issue [ 51491 ]
            Component/s Original: Issue - Assign [ 46514 ]
            SET Analytics Bot made changes -
            Support reference count Original: 12 New: 13
            Bugfix Automation Bot made changes -
            Support reference count Original: 11 New: 12
            Bugfix Automation Bot made changes -
            Support reference count Original: 10 New: 11
            Bugfix Automation Bot made changes -
            Support reference count Original: 9 New: 10
            Bugfix Automation Bot made changes -
            Support reference count Original: 8 New: 9
            Confluence Escalation Bot (Inactive) made changes -
            UIS Original: 2

              apawelczyk Artur Pawelczyk (Inactive)
              yokamoto Yuki Okamoto (Inactive)
              Affected customers:
              12 This affects my team
              Watchers:
              14 Start watching this issue

                Created:
                Updated:
                Resolved: