Was quick search updated recently?

[Brock Jolet]

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?

[Prashant Mali]

Hi @Subhash Haritwal ,

This error is throwing due to existing custom simple script validator.

Solution :

Check workflow of this project and edit that particular transition where you may see custom validator. you have do changes over their as per your requirement or remove that validator if you dont require.

Thanks,

Prashant

[Alexey Matveev]

Hello,

I think you have some kind of customizations in your Jira. What plugins do you have installed?

[Subhash Haritwal]

Hi,

Thanks for answer! i am having issue for a one project and able to add points for other project. what should i customization for that particular project?

[Alexey Matveev]

If you have ScriptRunner, then you shold look at the behaviours for ScriptRunner. If you have Power Scripts, then you should have a look for Live Fields.

Maybe you have another plugin. I am not sure, which ones.