Issue Summary
The new queue design introduces an additional scrollbar at small browser height (~570px).
Scrolling through the results causes the inner container to pause, then forces the user to scroll down again to make the outer container scroll.
Steps to Reproduce
- View a queue that contains enough issues to scroll through.
- Reduce the browser height until an additional scrollbar is created outside the results window.
Expected Results
A seamless scrolling experience at any browser size - comparable to the Issue Navigator or previous queue experience.
Actual Results
When a user scrolls through the list of work items, they reach the end, but can't see the pagination controls until they move their mouse to the outer scrollbar and scroll again.
This can cause a confusing experience for the users with lower resolutions or have hi-dpi scaling on.
Workaround
End users may be able to mitigate this behaviour by making changes at their OS level. See the following Bug Workaround step for instructions on how to enact this:
- is related to
-
JSDSERVER-6719 Improve column width in new queue design to improve readability
- Gathering Interest
- relates to
-
JRASERVER-70658 Double scroll bars in Watchers list
-
- Gathering Impact
-
- is cloned by
-
JSMDC-5587 You do not have permission to view this issue
- links to
[JSDSERVER-6726] New queue design introduces additional scrollbar at small browser size
Hi everyone!
I think another workaround is closing the list of queues to the left of the table by clicking the x icon on top of the list.
The only reason the rightmost scrollbar is shown is because the list of queues on the left is too long to fit the screen. For me this worked. When the list of queues is closed Jira displays a more compact way of changing the queue (a "Switch Queues" dropdown to the right of the queue name on top).
You can go back to the other list of queues by clicking "Keep menu open" in the dropdown (bottommost entry).
Hope this helps!
For me neither of the workarounds did not work
The workarounds don't work in Jira 9.12.15 Datacenter.
For me this happen in 'Search for issues' (in query/jql search)