New search UI is a downgrade. Its more clicks to do simple work task searches. This change is a result of over-engineering. When you could have just added a checkbox "search all these apps">
Sitting apps layer on top of search first is INSANE idea
Please revert. Absolutely no human being wants to click more and watch page loads more when searching for content. It worked great before.
Also to add, Atlassian licensing has just increased for what? So we have feature regression then wait years for functionality to come back again? Absolutely insanity.
The last line of @Phillip C's comment is pertinent here: "It worked great before"
If we're getting a side-grade with some UI adjustments, sure, that would be palatable. But this search is measurably worse in a number of metrics:
Readability and layout is worse and does not follow basic UX/UI design principles; features/abilities have been outright removed.
Number of clicks/button presses required to complete the same task has increased by at least 1 in many cases, and at worst 4 or 5.
Ability to retain context when re-interacting with the search bar, and related poor choices regarding hotkeys
Lackingconsistency with previously established norms/conventions on the site, including conventions established with the recent UX/UI update.
Parts of this update honestly feels like someone got an intern to put the site through Gemini Canvas and they got slop out the other side. It's hard to get excited about any of the cool new stuff when I'm stuck with broken basic tools. You can't use a drop saw if your safety glasses are falling off.
I hesitate to even say this because it sounds a bit ridiculous, but it feels like the soul has been sucked out of the platform. You guys have copped flak in the past for various updates and changes *cough server to cloud cough*, but this one might be different. Please take the feedback on board. Your long time users and admins aren't happy with this shift.
Atlassian Team members are employees working across the company in a wide variety of roles.
December 2, 2025 edited
Update 3rd December 2025
Hi all, again thanks for the feedback on this post and via in app feedback. I am reaching out to people who have submitted in app feedback and have left contact details. So if you have commented on this post and would like to talk to me please use the 'Give feedback' link in search.
Noted on the feedback at the extra clicks incurred by this new UI. While only a small percentage of people in Jira use filters (<2%) its clear that when you are using filters this new UI is missing the mark. We are now working on options to either save filter preferences or have suggested filters appear.
I'm pleased to share we've added the following features to the quick find UI:
Added more types to the Status filter
Added more content types to the Types filter
Then in Rovo search, choose the Jira app and then you will find the following new filters
Filter to show work items you have Commented on
Filter to show work items you are Watching
We are working on adding the assignee image to work items in Rovo search, adding extra meta data to search results, adding sorting + the filtering improvements noted above
Making a "One Click" solution (how it was before) a "multiple Clicks" solution is clearly not an improvement. Besides that - the recent Issues list is not working. It is showing completely irrelevant Issues. In summary ... this is broken!
This is awful. It doesn't work intuitively, it doesn't work as good. AI doesn't need to be in everything. IF it is, it needs to be BETTER by a long shot, not 100x worse. You have once again ruined my day and most likely my year. Nothing about this makes my job easier, it actually makes it harder because I CANNOT FIND ANYTHING NOW. Revert this or give us the option to NOT use it. I cannot explain how angry I am every time I open this god forsaken new search, just to exit out and bite my tongue - why use it? I will spend 10x longer doing something that used to take a few seconds. Why am I clicking 10000000x for a search function, i want to type in my SEARCH and then YOUR things do all the work on your end to make it show up.
What I can't find is a way to navigate directly to the Search page - the one where I can add a JQL query and perform actions on the results
There used to be a link in the search box drop down menu
Now when I do a search from the drop down it doesn't even go to the search page, it goes to some AI results page that doesn't have any of the tools of the old page.
But often I need to be able to do a precise selection of tickets via query, then operate on them.
This useful feature seems to be a hidden page now?
I absolutely hate this change. It took us like 10 years to get you disable this stupid "smart search query".
Then search was pretty much perfect. Jira search produced a useful grid of data that could be filtered and sorted as the user saw fit.
Now you created a "google" like search wall of text and it is beyond dumb.
Who do guys work for?
Do you demo these proposed changes to a target group of users before you roll them out?
Or do you just have thousands of product managers and developers and you constantly have to change stuff for the worst just to justify your existence?
Put it back.
From now on, if you want to waste time doing something dumb, build that dumb thing in parallel and give people the opportunity to use the new dumb thing.
"We are working on adding the assignee image to work items in Rovo search, adding extra meta data to search results, adding sorting + the filtering improvements noted above"
I think you lack a fundamental understanding of what you're building and for whom.
This is what you think you are building.
In reality, this is what you are building.
What you need to build, for us, and "us" being people who create software for business users to do work is this.
All this "rovo" nonsense and "smart search query" is just flashy trash that can't even get out of its own driveway.
What "we" need is the work truck. We need a tool that will help us get the job done. It is not flashy. It is not fast. It doesn't get noticed.
But if you need to carry a cubic meter of dirt, the work truck can and the "rovo/Lambo" can't.
If you need pull the Lambo out of a ditch, the work truck can and the Lambo can't.
If you need to deliver food, water, medical supplies, the work truck can and the Lambo can't.
And if you need to mount a M2 .50 in the back, the work truck can and the Lambo can't.
The old grid search, with multiple, customizable columns is the work truck. This new "AI" regarded rovo search is the Lambo that can't get out of its own drive way.
The 'old' search was easy to use and absolutely intuitive, so it would be great if people could decide for themselves which search function they would like to use. I'm confident that most users would opt in for the old search, me included.
Taking the amount of comments into account of people who don't like this feature compared to the "Likes" given I'd say that this is definitely a step back.
I'm sure if there were a "Thumbs down" button, the webpage would collapse because of all the negative likes given.
It is not returning anything for partial text matches and due to the varied nature of incoming tickets it is almost impossible to return robust search results. I need to find an old ticket quickly and can't. Was much easier before. This is operationally significant, is there a way of reverting back to the previous function?
Atlassian Team members are employees working across the company in a wide variety of roles.
June 4, 2026 edited
Thanks everyone for the continued feedback - I really appreciate you taking the time.
A few things worth clarifying that I think will help:
JQL hasn't gone anywhere. If you type a JQL query into the search bar and hit Enter, it'll take you straight to the Issue Navigator with your JQL applied. The new search experience (Rovo Search / Full Page Search) is where you land when your query looks like a natural language question rather than a work search - this is called intent detection, and I've written a separate post explaining exactly how it works (https://community.atlassian.com/forums/Jira-articles/Jira-intent-detection-community-post/ba-p/3199596). There's also a short video walkthrough on https://jira.launchnotes.io/ if you'd prefer to watch rather than read.
Having said that - the feedback that it's not always obvious why you've landed where you have, and how to get back to the Issue Navigator, is completely valid. We're actively working on making that navigation clearer.
I read every comment here and use them to prioritise what we fix next. If you're happy to share more about your specific workflow or what you were searching for when things didn't work as expected, please send in feedback via the 'give feedback' link and flag it's for me (Owen Wallis) - I'll reach out directly to set up quick call to learn more.
How hard is it to just put the old search back? It was not perfect but did what I wanted of it and above everything else, it was CONSISTENT, PREDICTABLE and REPEATABLE.
The new search is not consistent or predictable, especially with the new intent detection. Which is broken the second it comes into contact with the real world. I work on tickets in Jira. I search for guides and knowledge in Confluence. The combination of this new search and the change of language to "Spaces" and "Spaces, means I have the ITHELP Space, and the ITHELP space. how the is Jira supposed to contextually figure out what I am searching for?
I DO NOT WANT AN AI SUMMARY OF EVERY SEARCH I DO. How much wasted time and energy has been put into forcing this on me and everyone else I do not even want to start thinking about.
What's more, the same search query from a different location can result in completely different results.
Actually just making life hard. I hate using Jira now. Combining the above with the new stupidly flat and unintuitive UI that makes EVERYTHING look identical and unnavigable, and it's like you want to F off the entire development stack and just have us solve tickets by vibing at an AI.
Just stop it and give our f*ing tools back. The BARE MINIMUM you could do here would be give admins more granular tools to disable specific AI features so we can decide what is useful, and what is total slop nonsense.
I'm an atlassian admin at my company and have not been able to muster the will to defend ANY of these decisions since 2024. I used to bat for you guys but holy crap, you have made it so hard.
There are 3 pages of comments. And "JQL" is mentioned once on the first page, once on the second page. And 4 times on the 3rd page. 3 of those 4 mentions are by you.
What we want, and have been clearly stating is we want the old "grid" search back.
If you want to make some trash search as some type of pet project for you own ego, fine. Do so. But give us and option to default to the old search.
80 comments