Deprecation of Old Work Item Search Experience in Jira

[#1]

Hello Atlassian Community,

Last year, we introduced a new work item search experience, known as the ‘new issue search’. We will soon be phasing out the old work item search experience.

Why the Change?

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 community post 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.

What should I expect?

Nothing changes if you already use the new search experience.

If you still use the old search experience, here’s what you can expect:

• Starting from September 2025 we’re removing ‘Go back to the old issue search’.

• In November 2025 your work item search will be changed to the new search.

If you haven’t already, we encourage you to try the new experience. Our support team is ready to answer any questions as you become familiar with it.

Feedback

We want to hear your thoughts on the new work item search experience. You can provide feedback by commenting here or in our recent community post.

Thank you for your support as we work to improve Jira for everyone.

Best regards,
The Jira Team

[Abdiel Martínez]

"I'm looking forward to the new work item search experience. The performance improvements and updated interface sound promising. It’s nice to see Atlassian making these enhancements. Excited to see how it all works out!"

[André Matzke]

the "old" issue navigator has actually still more features than the new. For instance, I still use mostly the old, because there I can export to native Excel files.

Will the new issue navigator have also that feature by september 2025. Or will we, as in some other situations with new features, have less functionality with the switching off of the old function and be less well supported in everyday working life than before?

BR,

Andre

[Rhonda Morton]

I keep choosing not to go to the new version because I can't resize the list area.  I want to make it wider so that I get more items showing at one time, just easier when scrolling.  This feature would be much appreciated!  

[Roman]

No one in our company chooses to work with the new search as long as there is no simple to search for keywords in comments

[Oz Ben-Eliezer]

So you decided it would be a good idea to put a permanent 1+-inch tall ad banner for this new feature in the Issues page, reducing the available space for viewing *actual content*, presumably until November 2025?

Is breaking the old UI your strategy to get users to appreciate your new UI?

[Jean-Luc Lejoly]

I really prefer the old view because it is much more compact. With the new you get either to use a scroll bar or you have to reduce the columns and don't see the whole content or get it on 2 lines.

[Rafa]

here we go again..

[James D]

Another thing for me is that I tend to accidentally click back when I'm trying to collapse the sidebar when I'm in project settings, for example... 🤦🏻‍♂️

 

[Nathan Warkentin]

I tried the new one and everytime I tried to search for things, the stupid AI thing seemed to insert itself and seemed to get into a broken state. Can you please at least give the option to remove the AI stuff from it?

[Greymagic27]

I have a few gripes with this. The old one was much better and cleaner.

My main gripe is that when you middle click an issue, it focuses on that issue as well as opening it in a new tab. This essentialy makes middle clicking it useless as you lose your current focus. This worked as expected in the old issue view.

[Sue Lund]

I am happy that the date and time now show in the date/time fields.  I need that for Change Management.  I am going to try using the new view for a couple weeks, now.  I couldn't do that before.

There are a lot of things I like about it.

[Thomas Nilsson]

Please make it possible to close/hide these banners. You seem to have no concept of what UX is about.

[Jafran Majeau]

Please let us remove that banner.

And more importantly, please do not remove old search, there is literally nothing I enjoy about the new one, I can't find anything I want. It's support for complex search is worst. It's less customizable.

When you try to appeal to a broader market by sacrificing the user-base you've already established, it never works well in the long run.

You don't need to keep updating/patching the old search mode, just keep it available, it really shouldn't be that problematic.

There is nothing we enjoy about the new search mode in the company I work for. I don't even understand how you could come to the conclusion that it would be better.

Also blatant misinformation in your post isn't very helpful. There is NOTHING more user friendly about it. NOTHING. And saying "new features", when in reality you remove a LOT of features, and then add "new features" that essentially do less than the old ones, you haven't given new features. You've only removed some, regardless of the technicality you're hiding behind.

This is clearly a case where one of the following is happening:
-  You've been mislead by your marketing team that can only understand textbooks and seems to think that sacrificing what's good about your system to try to appeal to a market you currently don't have is the way to go.
- Or your current developpers are trying to solve a problem with how maintaining the current features/adding new one is problematic for them, and this is what they could come up with.

Either way, these changes are NOT made with users in mind.

If you want to add a new UI and new modes for whatever reason, that's fine, do it. But don't remove what works for your current users. That's bad practice.

[Luigi Flumian]

I simply don't like the new search bar. It uses more space on the screen and has less features, with those blue colors mixing the text and hiding most of the filters selected. With this new filter I see less data in the screen than using the old filter.

Everyone on my company prefer to use the old search box, as it is cleaner, easy to understand and easy to find the filters we need, without clicking on 10 different buttons to get there.

You are not doing one improvement, you are just making the UI not functional. Please try to listen to your end customer and keep the old search bar active for who wants it.

[Rob van der Land]

I dislike the new search. It's not faster and definitely not better. It does not search through the comments made on a ticket and therefore is mainly useless in our operation.

The UI of the new layout is also way more confusing. It's literally going from a good UI to an unimproved clunky UI with lots of unneeded buttons, options and whatnot on the left side of the screen. Currently it's clean and I can get to where I need in 2 or 3 clicks.

Let us keep the option for the old interface at all costs.

[Jago Philippens]

I have been using JIRA for 20 years or so. Please, for the love of the gods and all that is holy, stop fixing what isn't broken. Users of JIRA don't need a more 'intuitive' interface. We need to stop being forced to learn where our needed feature X is now hidden, if it's even available anymore. You cannot design an interface that is intuitive for all cohorts, in all organisations, all across the world. Stop trying.

[Josh]

Hi @Ivan Ran . A couple questions for you:

1. Is there a way for admins to see who is using the old experience?
2. Is there a way for admins to convert users from the old to the new experience?

Those two items would help us move the organization over to the latest experience.

P.S. We had a user report that they're unable to access filters today. Their account was set to the old experience as every filter URL had "&oldView=true" appended to it. However, we do not appear to have the ability via the user's account or as admins, to switch them to the new experience. An Atlassian Support ticket (CES-88185) has been raised for this but just an FYI.

[Jeremy Benson]

It's weird that the notice isn't dismissible even though the transition is all the way in November

[Brevin Pretorius]

Just echoing what the vast majority of folks are saying here: please do not remove the old search functionality. It is/was working as intended for all of our studio needs. Please listen to the folks who are taking time to share their feedback here.
Thanks in advance.

[Lina Cromer]

In the new search, the labels get truncated, and only the first label is listed, with a number badge to say how many other labels there are. As a team that uses labels extensively, the new search makes that field effectively useless. I tried using the new search just to get used to the change before it's forced, but I literally can't.

[JJ Simpson]

Can we add a method to show a "compact" view of the interface in this new version?

The newest update makes every single viewing pane feel cramped and like it is fighting for dominance on the screen. The decision to force every ticket have the entire subject line shown in Detailed View exacerbates the issue.

I'm also curious as to the decision to move starred search filters lower in the order. In all of the teams I work with, our starred(saved) filters are far more important than the default and unchangeable filters.

Moving starred filters lower in the sort list means that it now takes more movement on screen to find the information I need on the page.

[Lee Tappin]

Please can you remind me how to switch from the old search engine to the new search engine and vice versa. I am currently using the old search engine as when I tried the new search engine some months ago it didnt produce the required results as per my saved Jira filters. Thanks

[Achim Schupeta]

Wie kann ich denn auf die ‘new issue search’ umstellen?

[Ekaterina Dimitrova]

The new search is not cleaner and is less user-friendly. It stacks info in fixed-size columns, pushes data which is usually readable on a single screen out and forces you to scroll to the right. Cell spacing and margins are ridiculously huge. If you change column size, it does not always get preserved and a data  refresh makes you do formatting again. You are not really capable of saving a change in your filter on demand. Some fields with multiple entries (such as labels, fix versions, etc...) get stacked and not displayed on several lines so that you can see all of them. Even if you expand the column, they still don't get displayed, you need to hover over each of them. Native Excel exports require few clicks instead of just 1 as before. The sole feature that I find more convenient is the lack of paging if you have more tickets. 

Basically, you've destroyed a very convenient and clean search feature and have created a fancy monster which forces you to do excel exports if you want to look at your data. Well done, you! Going from live data analysis back to spreadsheet exports. Very clever!

[venkata sekhar palika]

I have a strong preference for the previous view as it is significantly more compact. In the new view, one must either utilize a scroll bar or reduce the number of columns, which results in not being able to see the entire content or having it displayed over two lines.