You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
When you navigate to the "Move Issue" page in Jira (/secure/views/bulkedit/BulkMigrateDetails.jspa), the page used to automatically focus the first element in the form as the "active" element from the browser's perspective.
This allowed the user to quickly configure the form and navigate to the next page in the flow using only the keyboard and by tabbing between elements.
For example in the screenshot below, the first dropdown would be focused so you could quickly move through the form.
Jira introduced some changes to its notifications system some months ago such that after page load, when the notifications AJAX request returns, the notification icon in the top-right nav has the browser's focus. To tab over to the first dropdown in the form requires about 5 tabs.
Same thing happens when move forward in the move flow. The page loads initially with the first form element focused but then the notification response is received and the notification nav item gains focus, annoyingly. Every page load requires you to tab 5 times to get the first form element in focus.
Since we don't have a paid account, I'm submitting this ticket here but it seems like a clear regression from recent changes.
Hi Todd, I can reproduce it, so I created a ticket with Support.