When a user opens a Jira ticket and double-clicks on a word or phrase to highlight it — a common action when reading, referencing, or copying content — and then switches to another application (e.g., a terminal, IDE, Teams, or any other tool), upon returning to Jira the ticket view automatically jumps to the bottom of the page instead of preserving the scroll position at the highlighted text.
This behavior is highly disruptive and frustrating, particularly on large tickets such as incidents, epics, or detailed bug reports that contain extensive descriptions, long comment threads, and multiple attachments. On these tickets, the user is forced to manually scroll back up — sometimes through hundreds of lines of content — to find the exact section they were reading or referencing. This completely breaks the reading and investigation flow.
Steps to reproduce:
Open any Jira ticket (preferably a large one with a long description or many comments)
Double-click on any word or phrase in the ticket body at the top of it, to highlight it
Switch focus to any other application (e.g., alt-tab to a terminal or browser window)
Switch back to Jira
Expected behavior:
The ticket view should remain at the same scroll position, with the previously highlighted text still visible.
Actual behavior:
The ticket view scrolls automatically to the bottom of the ticket, losing the user's position entirely.
Impact:
This issue significantly degrades productivity, especially during incident investigations and post-mortem analysis where users frequently cross-reference large tickets with other tools. The constant need to re-scroll is time-consuming and mentally taxing, making an already stressful workflow even more cumbersome.
Environment:
