Uploaded image for project: 'Jira Work Management Cloud'
  1. Jira Work Management Cloud
  2. JWMCLOUD-642

Scrolling down the list view keeps displaying the same issues in a loop when sorting is applied

    • 2
    • Severity 2 - Major

      Issue Summary

      When sorting is applied in the List view of a Jira Work Management project (for example; 'Status') and scrolled down using the mouse, the same set of results keeps appearing in a loop.

      Steps to Reproduce

      1. Create a Jira Work Management project
      2. Create a large number of issues
      3. Navigate to the List view
      4. Sort by 'Status'
      5. Scroll down the list 

      Expected Results

      The new set of results should be displayed

      Actual Results

      You will observe that every subsequent scroll keeps loading the same set of results

      Workaround

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

            [JWMCLOUD-642] Scrolling down the list view keeps displaying the same issues in a loop when sorting is applied

            @Jae-Hee Park

            OK confirmed.

            I understood.

            Thank you

            Kyusik Kim_김규식 added a comment - @Jae-Hee Park OK confirmed. I understood. Thank you

            Thanks 6a598a1e0a86 , In this ticket we have fixed the bug where the 'the same set of results keeps appearing in a loop' . Are you able to confirm that this behaviour is now fixed?

            We do have a different sorting algorithm applied for the `status` field. This is due to the fact that sorting by status in TMP is currently broken - please see https://jira.atlassian.com/browse/JRACLOUD-81183 for more information. 

            Jae-Hee Park added a comment - Thanks 6a598a1e0a86 , In this ticket we have fixed the bug where the 'the same set of results keeps appearing in a loop' . Are you able to confirm that this behaviour is now fixed? We do have a different sorting algorithm applied for the `status` field. This is due to the fact that sorting by status in TMP is currently broken - please see https://jira.atlassian.com/browse/JRACLOUD-81183 for more information. 

            @Jae-Hee Park 

            How can I apply this changes in our JIRA?

            I checked it but it's not fixed.

             

            Here is details about this bug.

             
            [Sort by “Key”]

            I expected that when I sort by “Key”, Jira sort all the 1896 tickets by “Key” and shows 50 tickets first and whenever I scroll down, + 50 tickets will be loaded and displayed.

            Actual result is same as expected.

            [Sort by “Summary”]

            I expected that when I sort by “Summary”, Jira sort all the 1896 tickets by “Summary” and shows 50 tickets first and whenever I scroll down, + 50 tickets will be loaded and displayed.

            Actual result is same as expected.

            [Sort by “Reporter”]

            I expected that when I sort by “Summary”, Jira sort all the 1896 tickets by “Summary” and shows 50 tickets first and whenever I scroll down, + 50 tickets will be loaded and displayed.

            Actual result is same as expected.

            [Sort by “Status”]

            I expected that when I sort by “Status”, Jira sort all the 1896 tickets by “Status” and shows 50 tickets first and whenever I scroll down, +50 tickets will be loaded and displayed.

            However, actual result was different.

            I think this system sort first 50 tickets by “Status”→ scroll down → Loading +50 tickets → Re-sort by “Status”

            Am I right? If so, this point is why I feel like a bug.

            If each sorting algorithm is different, please explain to us.

            Thank you.

            KS.

            Kyusik Kim_김규식 added a comment - @Jae-Hee Park  How can I apply this changes in our JIRA? I checked it but it's not fixed.   Here is details about this bug.   [Sort by “Key”] I expected that when I sort by “Key”, Jira sort all the 1896 tickets by “Key” and shows 50 tickets first and whenever I scroll down, + 50 tickets will be loaded and displayed. Actual result is same as expected. [Sort by “Summary”] I expected that when I sort by “Summary”, Jira sort all the 1896 tickets by “Summary” and shows 50 tickets first and whenever I scroll down, + 50 tickets will be loaded and displayed. Actual result is same as expected. [Sort by “Reporter”] I expected that when I sort by “Summary”, Jira sort all the 1896 tickets by “Summary” and shows 50 tickets first and whenever I scroll down, + 50 tickets will be loaded and displayed. Actual result is same as expected. [Sort by “Status”] I expected that when I sort by “Status”, Jira sort all the 1896 tickets by “Status” and shows 50 tickets first and whenever I scroll down, +50 tickets will be loaded and displayed. However, actual result was different. I think this system sort first 50 tickets by “Status”→ scroll down → Loading +50 tickets → Re-sort by “Status” Am I right? If so, this point is why I feel like a bug. If each sorting algorithm is different, please explain to us. Thank you. KS.

            A fix for this bug has now been released to production. 

            Jae-Hee Park added a comment - A fix for this bug has now been released to production. 

            Hi there, 
            A fix for this bug has now been released to production and this ticket will now be closed. Please let us know if this bug persists.
            Thank you

            Jae-Hee Park added a comment - Hi there,  A fix for this bug has now been released to production and this ticket will now be closed. Please let us know if this bug persists. Thank you

              89b9089d2927 Jae-Hee Park
              f1754156efb5 Vipul Reddy
              Affected customers:
              0 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: