-
Bug
-
Resolution: Fixed
-
Low
-
9
-
Minor
-
6
-
24 August, 2022
Hello Everyone!
This is now available to all customers who aren’t on Release Tracks. Those on Release Tracks will gain this functionality shortly. We’ve also made the PgUp/PgDown and Home/End keys functional in the Issue View.
Emily Ditchfield
Jira Software Team
Issue Summary
The keys to navigate (Up/Down/Home/PgUp/End/etc/) don't work in the issue view.
Steps to Reproduce
- Search for some issues in the Search Issue view.
- Select one of the results to view the issue
- Press the Down/Up or Pg Down/Up keys.
bug_navigation.mp4
Expected Results
Pressing the down/up or Pg Down/Up keys scrolls through the issue.
Actual Results
The Scroll container doesn't gain the focus when you click on it, unable to use the Keys to navigate.
Notes;
This also happens by simple opening an issue in the new issue view from other functions.
Workaround
- Reload the page.
- Use the tab key to select the area of the screen that you'd like to scroll at which point page up/page down will work.
- is duplicated by
-
-
- Closed
-
-
JRACLOUD-75899 Add Support for Page up/down keys in the new issue view
- Closed
- is related to
-
-
- Closed
-
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
[JRACLOUD-75167] Up/down and Pg Down/Up keys in the issue view don't work
This feature is now available for everyone!
In the modal or full screen issue view you can switch between the left column and right column using your left and right arrow keys (default to the right hand side) to enable scrolling on either side. You can also click on the right or left column to focus the scrolling to that side.
We won't be adding the Home/End or PgUp/PgDown arrow keys at this time to the shortcut menu, however if you feel strongly about this please feel free to open a JAC ticket so we can track interest! I'll now be closing this JAC ticket.
Jira Software Team
I've tested this again today - initially I wasn't sure it was working. But I think for some issues the right-hand (details) pane was getting focus on some issues - is this persisted somehow? Anyway, after some exploring I found the left/right arrows changes focus and I could then scroll the main pane.
The keyboard short-cut screen '?' does not mention the function of Home/End keys. Perhaps it should be added?
Hello Everyone!
As some of you have noted we’ve re-started the rollout process. This is now available to all customers who aren’t on Release Tracks. Those on Release Tracks will gain this functionality during the release on the 13th of October. We’ve also made the PgUp/PgDown and Home/End keys functional in the Issue View. We really appreciated your patience during the paused rollout.
Jira Software Team
Just tested this again on our Cloud instance - seems to be fixed for us. 
Is the rollout completed now?
Roll out has been paused, we will update on this ticket once all customers have the fix.
> describes how to see which track you're on - and change.
Which starts out with: Go to admin.atlassian.com. Select your organization if you have more than one.
So non-admin/regular users can do that? When I go to that page the only option I am given is to create an organization. I am not asked to select one.
As noted by Liron - follow the link to the Release Tracks documentation. This describes how to see which track you're on - and change. But only Premium and Enterprise customers change tracks.
@Liron, thanks for the update. The Release Track program is something I did not know about. So are you saying that all projects on the Continuous track should have this fix but Bundled track users will not until July 12th?
Is there any way for a non-admin/regular user to know which track their Jira Cloud instance is?
Thanks 6e687f59fb46 and 435803ee04f3 - you are 100% right. The feature is rolling out as we speak but takes a little longer for customers in the Release Track program. I will change the status back and we will mark it as closed once all customers have it.
My sincere apologies!
Liron
Seems like an issue shouldn't be closed until known affected users have the fix in hand and it's working for them.
Hi @Liron do you know when this fix will be deployed to all customers? Doesn't seem to be fixed for me.
Hey all,
This has been fixed in the new issue view.
Enjoy!
Jira Software PM team
This one is on the (long) list of usability problems with Jira Cloud found in our Cloud migration UAT. Thankfully our Cloud migration is blocked by other problems 
Page up and page down don't work on Windows 10 with Chromium based browsers.
Our company just transitioned to the cloud Jira, this was the first thing some on our software teams noticed.
This worked for 15+ years on Jira for all of us, and now doesn't.
@Dymytro - this works for browsing this ticket, but it does not work in our Jira Atlassian instance (Jira Software Cloud Premium) 
Great solution, Vivek! Atlassian should make you employee of the month 
This was driving me nuts today and it's clear Atlassian has no intention of debugging it, so I decided to do it for them. Luckily it turns out it's not even that complicated - it's a one line change if Atlassian decides to do. Just don't set tabindex to -1, it should not be set on such a high element as it causes this collateral damage.
So, if you don't want to wait for Atlassian to get around to it, what can you do? For those a little more technically inclined, you'll need an extension that allows running userscripts, I recommend Tampermonkey for FF/Chrome or Userscripts for Safari. Add the following code:
// ==UserScript== // @name Atlassian Don't Steal My Keys // @description Free your keyboard scrolling behavior from the shackles of JIRA's new view // @match https://*.atlassian.net/* // ==/UserScript== document.querySelector('[tabindex="-1"]').removeAttribute('tabindex');
Save it, and you may need to explicitly enable it too. But then if you reload any Jira page, your directional keys will magically start working again like they have been doing for eons, long before Atlassian was around. Hope that makes some of your days a little bit better.
> Created: 23/Sep/2020
> Status: LONG TERM BACKLOG
> Priority: Low
From all my experience with recent JIRA changes it means that the bug will be never fixed.
PageUp/PageDown is a basic native feature of any web page. Atlassian broke it.
Who needs these features? May be experienced Jira users? But who cares about them...
Hi, using the directional/navigation keys (page-up/page-down) for scrolling in a browser window has been a thing since the Internet was invented. This is so fundamental to the UI experience folks don't even think about it, until of course they realize its not there. Which was our case, and I'm sure will be many others as customers are forced off of Server. Is there any specific reason as to why this basic function does not work, is yet another security risk with Cloud? Even a single click on a section to focus there for the up/down keys to work would be common sense.
I see that this issue has been put into the long-term backlog as "it’s not as severe or pervasive as other issues.". You are aware that for every customer actually complaining there are said to be 10 others who just can't be bothered to say anything but feel the same? Seeing me and a couple of others struggling with this issue and thus commenting here, I am pretty sure there are much more users suffering in silence. UX related issues should never be put into some kind of long-term backlog, as they affect user every single day.
I too use a keyboard and avoid a mouse due to wrist strain issues. Not being able to scroll in issues because Jira's own JavaScript is busting things up is simply miserable.
I've just switched to a trackball from a mouse / trackpad due to a (non-RSI) sprain to my wrist, and this bug makes Jira almost unusable.
I can't scroll issues in the Kanban Board view at all using the keyboard, and without a scroll wheel I'm left with a narrow afterthought of a vertical scrollbar to click on.
Please fix ASAP!
It is completely ridiculous that you can't fix this. Just remove all your sorry javascript from the page. Even disabling shortcuts doesn't fix this miserable interface.
Please re-add this behavior into the new issue view.
There are often issues with several pages of content.
Tabbing 20 times just to use page navigation, or having to click the thin scrollbar, is not an improvement.
This change is also a pretty hard hit to JIRA's accessibility.
This goes not only for PgUp and PgDn; same problem for ArrowUp, ArrowDn, Home, End and possibly other common keyboard navigation keys and combo's (like Ctrl-Home and such).
https://jdog.jira-dev.com/browse/EM-2975 has been added to our backlog
I am still impacted by this issue, do I need to raise a new bug?