Number of Commenters with the "I'm New Here" badge: 37
Number of Commenters who registered with the Forums after this change started rolling out on apparently May 13, 2026 (@Andy Drucker was the first to report the bad news): 30
Number of Questions posted to these Forums about the change: 8 (that I could find)
Support requests filed about this change: ?? (Oh if only we could see this.
@Darryl Lee I would wager most people did not see this article when it was released, myself included.
I only found it when I started doing research when the change rolled out to our instance and users started complaining.
We don't even know if this has rolled out to all instances (some people appear to indicate it just happened on their site today). So there could be more confused people yet to find or even know about this change yet.
This new "feature" is horrible and inefficient. Why is Atlassian/Jira increasing the amount of clicks to get to an issue and making the product worse overall by eliminating detail view upon first click from list view??? At the bare minimum, at least keep keep full screen detail view upon first click of an issue from list view functionality an option a user can still enable as a user option/setting versus taking away the feature completely.
If you are trying to make your product less efficient and harder to use, you have succeeded, Atlassian.
I don't like these "preview panels" and can't disable it...
Any major UI change like this should have an option for the users to enable or disable it themselves, it shouldn't be forced on everyone across all instances.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
@Daniel Santiago not only would this vastly complicate the code base with multiple code-paths... adding more and more complexity over time, but it also makes the user experience more complicated.
Please bring back the detailed view which is easier to view than list view. Few of my colleagues also complaints about the new settings which is not user friendly
The new preview panel is significantly less convenient than the previous detail view and makes daily Jira work slower and more frustrating.
This is not just a UI preference. It directly affects productivity, usability, and the overall value Jira provides to teams that rely on fast issue triage, review, and navigation every day.
Please consider providing a global option to disable preview panels or allow admins and users to keep the previous detail view.
Please, please, pleaseget the Detailed view back. It's impossible to use the current view and I'm not the only one in my team who is suffering. This is just an option for user's convenience. This is terrible new experience to get used to these new unreadable panels I don't really need in my everyday life. I have quite extensive task descriptions and I'd rather be able to read them full screen as it used to be !!!!!!!
I have to agree that the recent update has introduced some significant usability challenges, and it is unclear how this approach was considered an improvement to the current workflow.
When managing a high volume of tickets, having each one open within a side panel and then requiring them to be popped out individually is not an efficient or user-friendly process. This change adds unnecessary complexity and slows down daily operations.
I would strongly encourage a review of this update, with consideration given to reverting to the previous functionality, as it provided a more streamlined and effective user experience.
The detailed view allowed me to get a quick overview easily once I filtered the tickets accordingly. And I was able to switch tickets using the arrow keys.
The new view forces me to click on the ticket links, which is only possible after scrolling the list all the way to the left again. All in all, that's a whole lot of clicking back and forth in two seperate panels in order to achieve the same result as before quite easily.
Luckily, I'm not a laptop-only user, otherwise the limited width of the right hand panel to half of the page max would bother me as well.
This was a HORRIBLE update. You removed excellent functionality - the ability to click to the first item on a list and then step through the list w/o having to open or close anything. Just hotkey j/k or use the arrows. Long jiras are very difficult to read in this new option and require tons more time scrolling. This negatively impacts productivity as well is being maddeningly bad UX. PLEASE have someone allow us to change back to the old way - even at the user level while keeping the new, awful option for those few use cases that need it. For anyone else reading this who shares this pain, here is the request for Atlassian to restore the original functionality. Please help make our voices heard. https://jira.atlassian.com/browse/JRACLOUD-96809
Progress is the forward movement toward a goal or an improvement in condition. Deterioration is the process or state of becoming progressively worse, weaker, or of lower quality. Forcing us to use a side pane without a toggle to swith it off is deterioration, I wish I wouldn't have to use Jira at all anymore, what a waste of time with this 'new' change. Why would you force this upon us, what makes you think this was a good idea? Perhaps if you have a 70 inch screen it makes sense, otherwise, bad idea.
First, pagination was removed and replaced with infinite scrolling, which works better on websites where users are meant to discover and browse content rather than search for specific information - which is exactly what the search function in Jira Cloud is most often used for in my experience. Not to mention that the information about the total number of issues in the full-screen filtered view has also disappeared, so there is no longer a quick way to check how many issues have already been reviewed.
Now the full-screen filtered view has also disappeared, leaving us with a worse version of what we already had (the detail view), where the end user decided which issue filtering view best suited the task at hand. (I preferred the full-screen view).
It’s sad that such major decisions regarding UX changes are imposed with the explanation that “we know better what’s good for you.”
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
What is UIS? "Our major products have dedicated bug fix teams who work solely on fixing issues we have shipped in previous versions of the products. The prioritization is done jointly by engineering and support, and is based on a metric called User Impact Score, which takes into account the number of users affected and the impact of the bug on their work. This way we're always working to fix the issues that cause the most customer pain first. We will continue to explore ways we can improve our communication in this area." --Jay Simons, 2017
wow! great! jira finally coming up to speed! been looking for something like this, and i've done a few workarounds [like having two browsers up side by side] but this is finally looking and feeling great!
Awful change. All the information I used to be able to see in 1 - 1.5 pages is now scrunched up with some of the text overlapping. Time to look at alternatives if this is the level of destruction we're going to get without it being optional.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
As Josh astutely pointed out it sure seems that Atlassian didn't learn their lesson from last year's debacle. This has not yet rolled out to our instance but as an admin I'm dreading the potential flood of complaints from my user base when it does finally hit.
I'd love to know your thoughts behind this, particularly given pretty much everyone else in the room is against it. I personally am battling over 300 JS and JSM users that are venting at me about this change, even though it was not something I did.
98 comments