Preserve expand/collapse hierarchy state when navigating back from an issue in List/All Work (NIN) view

XMLWordPrintable

    • 1

      Issue Summary

      After the List × NIN merge rollout for Premium/Enterprise users, the expand/collapse state of grouped parent items in the List (All Work) view is not preserved when a user navigates into an issue and then returns to the list.

      Steps to Reproduce

      1. Open a Jira Business or Software project using the List view (/list)
      2. Ensure the list has grouped/hierarchical issues (parent issues with child issues underneath)
      3. Expand two or more parent groups so their child issues are visible
      4. Scroll down to a specific child issue and click to open it (full page view, not Glance Panel)
      5. Click the browser Back button to return to the list
      6. Observe: All previously expanded groups are now collapsed. Scroll position is lost. User must manually re-expand each group to find their working context.

      Expected Results

      The expand/collapse state of all parent groups should be preserved, and the user should return to the same scroll position.

      Previous behavior (legacy List): If a user had expanded specific parent groups and clicked into a child issue, pressing Back returned them to the same list state, all expanded groups remained expanded and scroll position was preserved.

      Actual Results

      After returning from an issue view, all groups collapse and the user must manually re-expand each group to find their working context. This significantly impacts productivity for users working through large hierarchical lists (300+ issues grouped by parent)

      All groups collapse on back navigation. User loses their working context and must manually re-expand groups and scroll to find their previous position.

      Workaround

      The Glance Panel feature flag (nin_glance_panel) partially mitigates this by keeping the user in the list context when previewing issues. However, expand/collapse state is still lost when filtering or performing actions that trigger a list refresh.

      To enable for an affected customer, will need to contact Atlassian Support.

              Assignee:
              Unassigned
              Reporter:
              Souto
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: