Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,560,301
Community Members
 
Community Events
185
Community Groups

Was quick search updated recently?

I have a user that is reporting quick search functionality has changed. I can repeat her examples. Thus, I can verify the current functionality, but I don't know when or why the change would have happened. I don't often find myself using the quick search bar.

 

She purports that until recently, she could use the quick search bar to type the number of a ticket without specifying the project key, and only issues with that number would appear as suggestions. I have a vague memory of this working as well.

Now when I type, for example, "5856", instead of seeing "SDI-5856", I am given a list of issues as such "WC-1334, SOS-2933, SDI-3747, SC-4840, PDRA-7581, PDD-1912". I don't know what field it is querying as nothing in the short description appears to have the digits "5856".

If I type "5856" and then choose the correct option under "Filter by Project," the first result is the ticket I want to view.

 

We are also experiencing what appear to be illogical searches based on partial strings. When I search for "automatic" looking for a ticket with the summary "automatic payment," again, I get a list of suggested issues from many projects that do not have the word "automatic" anywhere in the descriptions that appear in the quick search window. 

If I type "automatic" and then choose the correct option under "Filter by Project," the first result is the ticket I want to view.

 

Looking at the official documentation (https://confluence.atlassian.com/jirasoftwareserver/quick-searching-939938728.html), Atlassian includes this line:

In many cases, you do not even need to type in the full key, but just the numerical part. If you are currently working on the 'ABC' project, and you type in '123', you will be redirected to 'ABC-123'.

This no longer appears to be true. (The documentation is for Jira Server, but we are on Jira Cloud.)

 

So did this change recently? If so, why?

What fields is it prioritizing over the issue key and issue summary?

1 answer

1 vote
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 19, 2023

Hello @Brock Jolet 

Here is the documentation for Quick Search in Jira Cloud:

https://support.atlassian.com/jira-software-cloud/docs/perform-a-quick-search/

By default the Quick Search will search the Summary and Description fields for the text you enter. That are keywords you can use in the Quick Search field to refine your search to look at other fields.

I find that when I type in a number it will search for that number in Summary and Description. It may also bring up an issue with that number in the issue key if it is an issue I have viewed recently.

If you want to search for recent changes to the functionality you could review the Blog posts that Atlassian publishes each week for changes released to the Cloud products.

https://confluence.atlassian.com/cloud/blog/2023

Thank you for your helpful links.

I've done some testing, and it seems that no matter what string I search, it prioritizes items that I have opened recently. I typed in the first four words of an issue summary, and Jira still listed nine other issues before the one that matched exactly.

Also, I don't know why the cloud search wouldn't search for a key when a number is typed in, as the documentation shows the server version will do.

For issues, your search will only show results from the Summary and Description text fields.

Luckily, I don't use the quick search often, but I can see why my users are frustrated.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events