nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Introducing the new issue search to Jira Cloud users (updated)

Kevin Yu

Say hello to a faster way of searching for issues in Jira as we’ve modernized and optimized this experience. While we haven’t made changes to the way you search for issues, we’ve improved the search performance in Jira, redesigned it, and added new features. With improved keyboard accessibility, everyone can search for issues without any hassles.

Group 278.png

Switch between views
Switch between basic and JQL modes
New JQL editor
Edit status without opening issues
Configure columns

What’s changed?

Read on to learn more about the new issue search experience, its features, its differences from the old experience, and information to make your transition to the new experience easier.

Search for issues faster

Keeping performance and scale in mind, we’ve backed the new issue search experience with a modernized technology stack so that you can search for issues in no time.

The new JQL editor

Build powerful searches using the Jira Query Language (JQL) to deep dive into data, create tailored views of issues for dashboards, and much more.

Fix errors in real-time

The new JQL editor can validate syntax fast, and highlights errors in red with detailed information on how to fix them.

Smart syntax highlighting

The new JQL editor helps you build queries in real time by analyzing your query structure, identifying entity types, and highlighting them as you type. This makes queries more readable, and easier to edit as you write.

Enhanced autocomplete

We’ve improved the autocomplete experience to give more insightful feedback as you type. The editor shows keywords and functions at the top, while loading the data in the background.

9f237777-c2fb-449d-951a-0fc4f75890d1 (1) (1).gif

Expandable editor

You can expand the editor to allow space for editing longer queries. The numbered lines make it easier to read the query and find where potential errors are. Additionally, you can add a new line as you type (Shift+Enter).

Edit status without opening issues

In list view, you can quickly change the status of an issue without opening it. Find the issue you want to update and simply select the status to change it.

Search across multiple projects

Add or remove projects that you want to search your issues from.

Configure and reorder columns

Add or remove columns to see your most important fields with issues in list view. Select Configure columns to add these fields.

You can also reorder your columns and customize your views as per your preference by simply dragging the columns to the right position.

What’s next?

We’ll begin moving all users on the old issue search (currently called the Advanced issue search) to the new issue search in Jira Cloud products (Jira Software, Jira Service Management, and Jira Work Management). Eventually, we’ll remove access to the old issue search. We’ll let you know about the key dates and upcoming changes well in advance.

Update

We're excited to announce that we're moving all Jira users to the new issue search experience by the end of March 2024.

We also support the following features making your search experience even more powerful.

Improved support for all fields

You can refine your search results further to find all the fields you need. To try it, select Issues > More+.

Configure more than just your default columns

Configure columns within your starred filters with just a few clicks. Select Configure columns > Filter to select the columns you want to see.

Admins can select Configure columns > System to quickly modify columns across projects for all users within their site.

Kapture2024-03-11at10.31.42.gif

Export only the issues you need

We’ve added more options to simplify your export. When using a filter, select Export issues to export filtered fields in the format you want.	When not using a filter, you can use Export issues to export your default fields in different formats.

Huge thanks to all our users for your feedback and continued support over the past year. We’ll keep you updated on further changes soon.

Comments

Dirk Ronsmans

Great to see/hear it's also coming to JSM now!

@Kevin Yu am I right to assume that the new JQL editor will also come to the Queues?

David Berclaz

Looks great, thanks for sharing!

Dave Mathijs

@Kevin Yu

Edit status without opening issues: What if you have a workflow/transition screen or a condition or validator configured in your workflow?

Kirk Gould

Sounds promising. Does this editor help us do the same searches in an easier way or does it also let us do more helpful searches?

Please search for all my Epics, along with their Stories, and Subtasks in hierarchical order so that I can see things as a structure, not just a list.
Please examine all Stories that seem to get stuck in a certain state the most so that I can identify bottlenecks.
Please find me Jira Issues by Project that represent Team Swarming the best so that we can copy that Team's approach.
Please search through all the Issues that have a similar workflow so that I can tweak the workflows to make them more standard.

Joey Lin

@Kevin Yu When will this change occur?

ridhima verma_qf33pe

it would be great to see all this in action soon

Martin Runge - XALT

I like the new and faster way of searching for issues and can not wait to use it. Thanks...

Mark Darby

Thanks for the updates. Always great to see improvements. As long as you're on a roll... nested queries would be great, too!!! Been asking for that one for a long time!!

Suze

With the ability to update status and the ability to edit issues, are users going to need to adhere to guardrails configured, such as workflow conditions, or fields on the edit screen?

Ian Channing_u6fhxb

Is it going to be any easier to get to/find this page?

As far as I know its still buried under 'Filters > Advanced Issue Search' - could this not be added as a small 'advanced' button in/next to the normal backlog issue search?

Pedram Mireftekhari_us7twx

The new view, does it support Asset fields as well?

Yatish Madhav

Nice. Thanks for this @Kevin Yu - I like it. I wonder if the view (JQL/Basic and Columns, etc) make the view personalised to the user viewing it or if it is changeable for everyone for a project/view? Also, how will I know this change is rolled out to me? Thank you

Erki Tammik

@Kevin Yu

Some of my thoughts

It would be helpful for admins to have presets for column layouts. Often, I find myself assisting people in different projects, and I need to frequently modify the columns to view relevant information from their specific projects. Having preset column layouts would make this process easier.
I would appreciate it if the advanced issue search could be made more easily accessible, preferably through a shortcut. It would also be nice to include it in the command palette menu

Jordan McCombs_lmkcqj

Love this, but are we ever going to get improvements on the way we can search for linked issues in JQL??

Haddon Fisher

Is the new JQL experience functionally equivalent to the current "Advanced Search" JQL search or are there things still missing from the new experience?

I am a pretty big fan of the UI\UX improvements in the new JQL search experience and have been waiting for it to be promoted to top billing, but it seems like whenever this happens there's a small number of highly important features that get left behind.

JQL is incredibly important to how people interact with Jira, so I am really hoping everything is there. Not to say I wouldn't welcome some much needed improvements, but if we've waited 20+ years for some of these (as much as I hate to say it) we can probably wait a few minutes longer.

Doug Harris_oe8ocf

Does this need to be enabled in some way? I'm not seeing the syntax highlighting or error indications shown in these screenshots

Dave Furlani_2zy3uu

Looks good. I wish the JQL editor autocomplete would add the space after each field/phrase/text is added so I could just build a query with the mouse and didn't have to hit the space bar every time, but maybe that's just me being lazy

Serosoft Jira Administrator

Great features! When can I see at my Jira cloud?

Diogo Teles_zhgoui

This is great! I was always a bit sad that JWM has such a powerful issue list view and in JS filters and issue view you still could do no issue editing from the list. This is not quite that yet, but look like a step in the right direction.

Also, that expanded JQL rocks

Brecht Seys_u8wrsi

Native partial search matching for component and/or not breaking Scriptrunner so I could still use "component in componentMatch(regex)" would be great.

Chris Tolley

@Kevin Yu we have noticed that if you include to show the "Label" column, and your issues have more than two labels in the new view, the labels start stacking on top of each other, making that issue's row larger. This ends up negatively impacting the screen real estate and you end up with a lot of wasted white space on the results page.

Is this something that can be changed, so that the labels column (and others) can be made wider to accommodate for that stacking of labels? Would then look much nicer.

Thanks

dan_hersonsky

Thanks for presenting this.

What about fileds that still cannot be presented as columns ?

We got a message that not all fields has been configured to columns.

Thanks a head

Jordan Koukides

@Dirk Ronsmans We appreciate the enthusiasm! We are currently assessing demand for this functionality (including the new JQL editor) in both JSM queues and queues config, however this experience will initially be available in JSM via the 'issues and filters' tab on the sidebar.

@Dave Mathijs Editing the status of an issue inline in the list view is designed to carry over all of the same behaviours as editing the status within the issue, including obeying transition screens or validators. Please let me know if this is not working for you.

@Kirk Gould The new JQL editor still uses the same functionality that our customers know and love, however many of the upgrades have been made to the user experience (ie, syntax highlighting, user lozenges, improved error handling, etc). To better solve for the use cases you've mentioned, definitely check out our Atlassian Intelligence features which are coming soon. I think our new solution for converting natural language queries to JQL will be a great demonstrator of your examples.

@Joey Lin We are rolling this change out progressively based on the features that we currently support in the new experience. The majority of Jira Cloud instances should have this updated functionality as of today, however customers who use the more complex issue search features in the legacy experience may have to wait slightly longer so we can ensure that we have complete feature parity.

Jordan Koukides

@Ian Channing There are a few ways to access this screen in Jira Cloud.

Searching within the context of a project:

Navigate to a specific project -> In the sidebar, click 'Issues' (or 'Issue and filters' if you are in Jira Service Management)

Searching within all issues in an instance:

Navigate to the 'project context' issue search as described above -> Click 'Go to all issues' at the top of the page
From the top Jira navigation, click 'Filters' -> Click 'View all issues'
From the top Jira navigation, click the search box in the top right corner -> Click 'View all issues' at the bottom of the pop-up (or just press 'Enter')

@Pedram Mireftekhari This new view does not currently support the Asset field, however it is on our roadmap to be included in the near future.

@Yatish Madhav Currently, configuration of columns is only stored on a 'per user' basis. We are planning to add functionality to configure columns for a specific filter, and also bring the capability for admins to configure columns for a specific project or instance. You can check if the new experience has been rolled out to you by following the instructions to find the page at the start of this comment.

@Erki Tammik Responses to the comments above should also answer your questions.

Jordan Koukides

@Jordan McCombs Appreciate your feedback on this - linked issues functionality is definitely something that we can look into. In the mean time, I would suggest trying some of our third-party apps that bring additional functionality to JQL, such as ScriptRunner for Jira.

@Haddon Fisher I can confirm that JQL functionality of the new editor is the same as the old editor behind the scenes - the only changes are updates to the visual UX, as well as usability improvements to autocorrect/suggestions and error handling.

@Doug Harris We are rolling this experience out on a staggered basis dependant on the features that we currently support and the features that your users have used recently in the legacy experience. However, this is available to everyone for searching within the context of a specific project, accessible by:

Navigate to a specific project -> In the sidebar, click 'Issues' (or 'Issue and filters' if you are in Jira Service Management). If you do not see Issues in the side nav, you may have to configure it in settings.

@Chris Tolley We share your sentiment on this Chris - pleased to report that an improvement to the labels field will be rolled out over the next few weeks to alleviate this issue.

@dan_hersonsky Our focus is on progressively adding more fields to the new experience that can be configured as columns within the list view. Can you please share the specific fields that you are looking to use?

Randy Padgett

Using the new Jira Search we are experiencing an issue when trying to export the data to Excel CVS and get the following on a new browser tab:

Is anyone else having this issue? We also noticed that the option to export current fields is not available in the drop down, only all fields is the option.

Kristján Geir Mathiesen

Hi @Kevin Yu and @Jordan Koukides

So am I understanding correctly that the the old issue search (currently called the Advanced issue search) will go away totally and instead, the new issue search (found in each Project panel) should be used?

Thanks,
KGM

Jon Metelonis

It seems that the changes outlined in the section What's Next: "We’ll begin moving all users on the old issue search (currently called the Advanced issue search) to the new issue search in Jira Cloud products" have already rolled out.

Advanced search is missing in our instance and many users are confused and disappointed. The new search presently lacks features they found very useful - these are now listed as "upcoming features".

Am I correct in my understanding? or, should I open a support request?

Thanks.

Hugh Gibson

I can see the old issue search in our instance, accessed via the quick search bar. But the Issues list for a project is using the new issue search, and is prefilled with JQL to only show tickets for the project. This can be overridden to show tickets across all projects (absolutely essential for us - I rarely use the project-specific issue list).

The original posting mentions updated technology. Seems that is all in the browser, and nothing in the back end. That's disappointing, as one of the biggest failings of search in Cloud (vs Server) is the removal of sort by relevance for text search. See https://jira.atlassian.com/browse/JRACLOUD-80173

Michelle Kappauf

Can't wait for the rest of the columns to be available. Is there a reason the Due Date column shows the day before the due date that is actually set on the issue?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Unanswered
Groups
Help

Find more posts tagged with

jira

cloud

jira-cloud