I do not use the new search view as it does not allow me to import the search results in an excel format that is essential for the worksheet that I incorporate those search results into. Until the new search view allows me to do the same, it is going to create a huge issue for me.
The main complaint so far from my users is the consolidation of the WORK value. They like being able to separate the issue type, key and summary into different collums.
Date fields need to be changeable between straight dates and relatives dates (such as "2 days ago" or "tomorrow"). I find both useful for different things (relative dates are nice for grouping issues which are ready to be evaluated for their next step). Having to switch UI entirely to toggle this feature is silly, esp considering documentation says "just click the date to change it" ... I guess that geature didn't survive either.
Atlassian, I don't know if you collect statistics on what percentage of users switch back to the old but if you do and if the numbers indicate that a large number of users are explicitly switching back to the old, that should tell you something right? If you are getting all these negative comments about the new search and users are switching to the old, maybe reconsider your plans to hamstring your users?
The new work item search is modern, faster, and easier-to-use. It’ll enhance performance and your Jira navigation experience. Key benefits are outlined in our previous and include:
- Faster Performance: Quicker load times and less delay.
- Better User Experience: A more intuitive interface.
- New Features: Access to advanced tools for managing work items that the old navigator didn’t have.
As business user, I do not need a fancy tool. Instead I need a tool which is usedful to work quick and efficient without bells and whistles. For me the good old search has many advantages.
- Faster Performance: use as few mouse clicks and type in with a small number of user interaction.
- Better User Experience: use as few mouse clicks and type in with a small number of user interaction.
- New Features: The old one is sufficient. Any new feature need more screen space, requires extra user interaction. AI may be good for some things. But in my company it is a must to keep the data out of machine learning data sinks.
My summary:
I don't need this new search.
The new search slows down my daily work.
Stop the unwished deprication of the good old and working search.
Looks like there is a misunderstanding about the new search experience.
There are two new issue lists. One new issue list appeared in the project view with a really new user experience and no JQL. It is nicer but has less features.
It is frightening to test. The switch at the admin GUI tells: "Move all users to the new search"
Would be much better to have a switch: enable all users to try the new search experience (with the option to switch back any time to the old one individually)
There is another new search experience. This one is not so intrusive, at first glance looks like a simple change in graphics. It has JQL. For me, JQL means it has all the features we need.
It seems like a terrible rollout of a new feature. For me, as an administrator, the option was to convert all our users to something new we do not know. And it was something that was easy to confuse with another, similar but more dangerous change.
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.
Atlassian Team members are employees working across the company in a wide variety of roles.
July 7, 2025 edited
@André Matzke New issue navigator has the same export options as the old issue navigator in the ‘Export’ dropdown. If you were using export through an app, the apps have been moved under ‘Apps’ dropdown in New issue navigator. Hope this answer helps!
@James DThere are no changes to the issue navigator in project setting. This deprecation applies only to old issue navigator in global setting.
When using the search field in basic mode in New issue navigator, results will be based on the summary, description fields, and all text fields. To search comments and worklog too, select More+ to view additional field filters, then select Text.
Please add your vote or comments regarding this issue here: JRACLOUD-84332 - Roll back to original search bar in issue navigator.
Your vote helps us prioritize improvements based on customer demand. We appreciate your input and encourage you to follow the ticket for updates.
Currently there is no way for admins to see who is using the old experience. Admins can select ‘Move all users to the new search’ under ‘New work item search transition’ in Jira Admin settings → Work Item settings, but individual users can still opt out to the old issue search until it is deprecated in November.
"Move all users to the new search" option will still allow individual users to opt out of the new experience until September. The new search experience is the second one you mention in your message, with JQL editor and features available in the old experience.
Calling this an improved user experience is a farce. It is a regression that the new basic search no longer includes searching for text in comment fields. While many of us are comfortable using JQL for searches, many more users are less comfortable and only use it sparingly or when required. Searching the basic fields (yes I think basic goes beyond Summary & Description) for a simple text string should be included in the BASIC search.
Atlassian, I'll be frank with you (just like everyone else you've angered with your marketing-speak feature rollout): This is abysmal.
Key staples of navigation I've used for years are now slower, more cumbersome to use, or arbitrarily (re)moved to shove AI down my throat. I had workflows that served me, your paying customer. And you've taken them from me. Why should I keep using your service?
You need to fix this and roll it back, or provide a toggle for the old UI.
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.
@Ivan Ran Can you explain the stringification of type, key, and summary? I regularly omit the type column from filter results, and I want the ability to sort by type (when I include it) or key by clicking a column header.
What purpose does coercing them to a single column when they're obviously still discrete values serve?
I can't figure out the new search interface at all. How do I add new search criteria? Literally can't figure out how to just search for issues I've entered. How is this "more user friendly?"
ETA: just got informed I got an "award" for this post. Seems like someone whose struggling with some aspect of your product is really not interested in how you've gamified the experience of trying to communicate to you about your product. If I'm on your support and feedback site, I'm probably already frustrated, and really not in the mood for hollow attempts to make interacting with your forum "fun."
The New feature re-order our columns in filters without consultation, it seriously impact out work as we've set number of excel & power Bi chart which rely on the order of the filters.
You have mentioned: - "Our support team is ready to answer any questions........" - Support team has not responded/replied to any of the questions/concerns raised by people wanting the old feature as is.
Every feature has pros and cons. Old search feature has nothing wrong with it, even in terms of performance. So removing it totally is an incorrect idea.
Why remove it? when people want it? Let us all keep the old feature as is, in settings, where "&oldView=true" parameter is added to the URL.
Atlassian should keep this feature as is.
Those who like new feature, use that one, those who like old one, use that one through settings.
If you want a good AI-generated summary about why this such a problem, just type "why is everyone so upset about the new global issue navigator in jira?" into Google. I'd highly recommend this exercise to the Atlassian dev teams and product managers.
"Improved" is a inaccurate description. The previous version was more useable, easier to navigate and view/edit. This isn't a case of 'getting used' to it. It's a case of bad design/functionality. Please revert.
A minor inconvenience now; when I duplicate a tab earlier, if it was in the Issue Navigator page, it would duplicate the pages as it, so jira search was easier. Now, when I have to open multiple tabs for each or duplicate, I have to click the search filter each time.
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.
I learned last week (from an Atlassian) that the current plan is to further abstract search away from SQL-style querying.
This is a mistake. In a lot of companies, one reason the end users don't create their own filters or board queries is because they request them from Admins, and we need to be able to tailor those filters and queries to our users' needs.
I've said it before and I'll say it again - just because Admins are a much smaller population than our users doesn't mean it's smart to ignore us, or to downplay our needs. We're the conduit through which the end users interact with your product. Making our experience worse will not make theirs better.
79 comments