Is anybody from Atlassian reading this thread/forum? It seems that end users complaints are really and deeply ignored :-( What shall we do to get attention and professional customer care that values customers?
> What shall we do to get attention and professional customer care that values customers?
Start looking at other products? :)
I'm only half joking. Too many disappointments in the past couple of years, and it's just getting worse. It feels like they feel they are too big to care about the constant repeating interruptions they cause the workflows of their pesky customers.
I've already started casually examining some other options.
I did not want to be so explicit with looking for the new software... Unfortunately it's not so easy to migrate to another tool... I passed it couple of times and it always was expensive process with some data lost...
I'd rather stay with Atlassian and continue using Jira and Confluence.
They have many strong points, and we also have some API integrations with them we'd have to migrate together with the data itself.
I'd also much rather spend my time on my actual work.
I just find it so frustrating that things keep breaking, and reports on regressions (or de facto regressions) seem to always hit a wall of "oh we are so sorry and totally feel your pain, please go vote for some ticket that will never ever actually get implemented".
It's not about missing a couple of features. It's about having things repeatedly break. In my company if a client reports a regression in a new release then we give it a high priority - even if it's a small issue and even if it affects only a small portion of our users. Atlassian seem to often just let these issues starve...
I understand that the old navigation is being replaced by the new one. But I don't see why that banner needs to be shown all the time, even when I'm still using the old navigation...
I dislike the fact the your starred or saved filters are not in really any order. I specifically named my filters a certain because they were in alphabetical order and easier for me to find. Now most of my more commonly used filters are not displayed on the side panel so i have to go looking for them. I cant rearrange the order and renaming doesnt seem have any impact. I dont want to see by recently used. i want to see by a specific order of ones i used most to least.
I have tried to find ways to reorder in manner that i prefer but havent found that info. If its available please share. Otherwise make this an option so I dont have add extra steps for something that should be very simple.
Not only does Atlassian have no grasp of good UX, they also apparently lack an understanding of calendars -- so I'll spell it out for them:
The original post clearly says:
"Starting from September 2025 we’re removing ‘Go back to the old issue search’."
As of this morning (July 30th, 2025 -- over a full month before September), I no longer have the option under the "Labs" to revert this awful UI. This option is now completely gone
Thanks, Atlassian. I feel both heard and clearly communicated to.
@Greymagic27 we have literally created a Chrome extension to "fix" Jira. But we've pretty much given up on it as our fixes keep breaking with every update (read: regression) Atlassian releases (which is like every other day...)
Working with new filters in Jira has become extremely inconvenient.
What used to be simple and fast is now a frustrating experience.
Main issues:
Not all starred filters are displayed - to access the full list, I now have to open a separate page, which adds unnecessary friction.
Starred filters are sorted by date added, not by name, which means I can’t organize them in a meaningful way. Important filters added a long time ago are pushed out of view.
There is no way to sort filters manually or alphabetically.
The Recent filters is unreliable. Even after using a starred filter all day long, it didn’t appear in the recent list.
The default system filters are always expanded by default, even though they are never used, making the interface more cluttered.
Glad to see Jira evolving and improving the search experience. The new search is definitely faster and more intuitive. It would be great to ensure that all critical features from the old search are fully available and stable before the complete deprecation, so teams with complex workflows can transition smoothly.
Why on earth do you call tickets "work items"? And the new search is slow, horrible and the lazy load makes it next to unusable (for example, browser-based Ctrl+F / Search doesn't "see" tickets off of the screen). Apparently Atlassian no longer eat their own dog food as they used to 15+ years ago :-(
@Martin Blazek maybe it was inspired by Microsoft TFS :)
"Work Item" is much better than "Issue" IMO. That may be the only change Atlassian has made in the past few years that I find useful... Though "ticket" would be better.
You've recently forced your new issue browsing methodology in advance despite your supposed deadline. Users are stuck in this mode already. It seems November 2025 does not start at the same time for JIRA as for the rest of the planet.
It is so, HORRIBLY slow, it is very frustrating for me and several others where I work. We wait for the pages to load. They don't. Then we attempt refreshing them, sometimes for minutes on end, to no avail. Sometimes it takes so long I just give up and work with what I remember and try again a few hours later. Sometimes it works then, sometimes it doesn't.
That is a deal breaker for us. If you can at least tell us if you're working on improving this (so we can have an experience similar to the speed of the old issue search), that would be helpful. But if you are genuinely satisfied with this change and think this is an, and I quote, "This offers a faster, more optimised Jira search", then we are going to look for alternatives.
I strongly prefer the previous view. In the example below, the New Search View does not display the full verification details. Additionally, it appears to ignore line breaks (\n) compared to the Old Search View. Is this something that can be addressed?
Atlassian Team members are employees working across the company in a wide variety of roles.
August 19, 2025 edited
@Peter Farrell Looks like the option in your screenshot refers to New Navigation in Jira, not the work item search, apologies if the terms used are a bit confusing. You are still able to switch to old work item search by clicking on the meatball menu in the top right of the work item search page and selecting 'Go back to the old search'.
@Rustam Baladai New work item search has the same filter configuration as the old work item search, the changes you refer to are caused by New Navigation in Jira. You can find out more in this page.
Only one label is shown in the new view. We use labels heavily, and this regression is really hurting the workflow. (It is also true for other fields, like "Affects versions"...). In-product feedback seems to go to a black hole, with no response whatsoever, and the ticket https://jira.atlassian.com/browse/JRACLOUD-83652 did not move anywhere in 16 months! This is a huge regression and must be fixed (or at least proposed as an option).
Another thing which bothers me greatly is the introduction of infinite scrolls throughout the Jira interface. In practice, it means I can't use browser search anymore. It is difficult enough in the backlog (I am learning to use the search field instead, but in my opinion it is an inferior option because (a) it hides other results and (b) it only works on certain fields), but in the filter results there is no such thing as a "search field"!!! Before, if I had let's say 3 pages of 50 results in my filter, I could try 3,5,10 searches over all the results in seconds. Not possible anymore. (The only way, a very slow one, is to modify the JQL by adding your extra search in there). In short, there is no correct solution for search now.
Also, all those infinite scrolls are about 3-5 times slower to show up on my computer than the old view. All in all, huge regressions all around.
I understand the need to move forward, and even if the new navigation slows me down for the moment because I am not familiar with it yet, I am willing to concede that maybe it is actually better than the old one. But a company such as Atlassian must be very, very careful when removing features / introducing regressions. It hurts the customers more than any value brought by the new features can compensate. I can't move our 150 users and dozens of projects to a different solution in a blink of an eye, but the more they make it harder for us to work, the more likely it is going to happen.
I'd like to add my voice to the >9 pages of similar comments that for me the new search mechanism is missing so much functionality compared with the current (old) feature that we'll probably end up scripting for the information we need to find instead. This feels like a pivotal moment and an indication of the end of life for Jira usage as we know it. It has been very good while it lasted. Thank you for everything you've done. All best wishes with the rollout.
@Ivan Ran, will you take into account all those comments and stop the rollout of that feature or does Atlassian sticks on November 2025 to activate it?
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 Leaders.
@Jean-Luc Lejoly I have it on good authority from a member of Atlassian's UX team that they're looking to move away from the SQL-style "query your own database" model of interactions, which makes me unbelievably sad.
I LIKE knowing where my stuff is and knowing how to get it, and I loathe the directions Jira has been moving. :(
99 comments