Jira searches all Text-Fields. Number fields are not searchable via quicksearch. see also: https://confluence.atlassian.com/jiracoreserver073/quick-searching-861257204.html

 BTW: this is an 16 year old issue which was resolved in 2012 (Jira Version 5.2)

I am unable to search custom fields using the Search bar. 

and Advanced search returns results but this defeats the object of having a quick "Search" function. 

I have a Jira server Jira v8.10.0 and I can't search custom fields using the quick search in the board's top right search bar. Am I missing something?

Hello.
I am a novice administrator.
I have a question that archs with the decision how and where should I insert it so that everything would work for me? thanks for the answer.

Hi guys,
As of 5.2 JIRA will search across all text based fields when querying from Quick Search and from Simple Search.

Cheers,
Nick Menere
Lead JIRA Product Engineer

additionally, we should also be able to search by number, by specific dates (like in JQL). Quick search shouldnt be limited to just ticket number (with PKEY), title and comments.

guillaume_c, thanks for the feedback.

No I was initially referring to the ability to swap between advanced and simple searching, however that is now no longer in scope and I have updated my feedback comment accordingly.

The proposed solution look good.

When you say "at least for the first implementation of this" does that mean that in a second implementation people will be able to search for text in any field in the simple search, so the quick will be able to return in simple search? Because that would be great.

Proposed solution sounds good.

I am with Mikael: I just want it to work. Like John we are also double-entering text into descriptions to allow for searching.

I am not in a position to validate if the solution proposed is the best one. If it works it sounds good to me.

The "text ~ foo" solution is fine for us. My original comments are way up at the top by now, but the main use case for us is that we have a custom ID field "Tower Id" with values like "NC2000". If a user fills it in and then does a quick search, it won't find the issue and they either file a bug report with me or they assume there's no ticket and create a new one. The workaround has been to also put the id in every ticket summary (like "NC2000 Test Ticket") but that is not ideal. If someone forgets to do it, we have the same problem where they assume no ticket exists, since people usually put the id in the summary.

From my perspective, the quick search box should be straight JQL. Anyone who has spent more than a day working with JIRA knows what s/he wants to search for. The Smart Query short hands are band-aids that'll hurt JIRA in the long run. It is probably worthwhile to consider making the Quick Search box a straight JQL box from the user Profile. That'll shut me up and avoid annoying the people who like the Quick Search box just the way it is.

I just want it to work, the solution behind i personaly don't care about.

I also think that the proposed changes would be a good solution.

The proposed solution would be a good step for starters Roy Krishna.

Cheers,
Joe

Unfortunately not mikaelhagberg.

However I'd love to get some feedback from all users watching this issue for our proposed solution I mentioned earlier:

Will this be fixed in v5.0?

We also want to get this fixed, however we have limited resources at this time.

Our plan is to change the quick search behaviour to be the equivalent of text ~ foo in JQL and the results will be in Advanced view (JQL) only (at least for the first implementation of this). Please note that this means that quick search will search the environment field.

Any feedback to this proposed solution would be welcomed.

Cheers,
Roy

I'm really curious why it's taking so long to solve this issue. So many comments, so urgent calls to solve it, dozens of votes. Even one patch from community member. Hey, Atlassian, do you really need more feedback to do it?

Would be GREAT!

The issue with using JQL is that if you want your search to include the issuekey field, it throws an error if it does not find the issue key. Is there a way around this?

Thanks for the idea goran.

In my case, I only needed a way to search quickly for one custom field, so implemented it through a Bookmarklet.

The following javascript will search a custom field called "Story points" in all projects, but you can easily transform it to your needs, thanks to the search permalink in JIRA.

javascript:d=document;t=getSelection()+'';if(!t)%7Bvoid(t=prompt('Enter%20story%20points...',''))%7D;if(t)%20location.href='https://www.YOURJIRA.com/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=%22Story+Point%22+%3D+%22'+encodeURIComponent(t)+'%22';

Cheers

Here's one idea:
Add a text gadget with the HTML containing at least one input box and one button/link. Add javascript to build the correct JQL-based URL which would search for appearance of the search term from the input box in all the fields of interest for you. Then open the window using the built URL and off you go!

We need the ability to search custom fields with the quick search. We are currently JIRA and Confluence customers, I hope this can be resolved quickly, since someone else has provided you with a patch. This seems like something that should be as easy as changing a configuration file for the end user.
Thanks

hello Atlassian,

will there be done something in this case (further versions)?
I don't understand why this issue is not assigned since YEARS !
Please, please, please create a configurable Quicksearch.

Chris' suggestion is no solution for us... too incomprehensible

regarding Chetan Sarvas patch: will it work in 4.2.1 too ?

I have same problem, I need to search issue by customers id. I think that what Chris suggested in 03/Jun/10, work just fine.

Hi,

To download the source code of JIRA, please access this page: http://www.atlassian.com/software/jira/JIRASourceDownloads.jspa

To know how to build JIRA from source code, follow to this article: Building JIRA from Source

Best Regards,
Thiago Auler
Atlassian Support

i have no source code of jira , what i can patch my 4.1 installation?

Use this patch AT YOUR OWN RISK. I have tested it only against our own internal requirements and it meets our needs. Whether or not it works for you is a different story. You are welcome to modify it as I'm releasing it under the Apache 2 license.

I'm still a bit unclear on where to submit a patch so I'm posting it here for now.

please Atlassian, make this patch available for all.
This is a very serious issue in IMHO and I dont get it why it is not solved by Atlassian IN THE LAST 5 YEARS ???

@Chetan Sarva

Hi Chetan, thanks for your enthusiasm.

I wrote a patch against 4.1.2 that implements this functionality. I'm not clear on what the licensing is around the source download, so I'm not releasing it. Can someone from Atlassian clarify?

Here is an article explaining how to send a patch to Atlassian.
http://confluence.atlassian.com/display/DEV/How+to+submit+a+patch

Thanks for your contribution.

Best Regards,
Thiago Auler
Atlassian Support

PLEASEEEE
I NEED IT !!!!
send to me !!!! PLEASE !!!! My supervisor want to KILL JIRA because this issue !!!

send to dyego.carmo@go-java.com , PLEASE !!!

I wrote a patch against 4.1.2 that implements this functionality. I'm not clear on what the licensing is around the source download, so I'm not releasing it. Can someone from Atlassian clarify?

Wow... this issue has been open for 5 years now?!?!

More one...

Please Atlassian , solve this very big problem...

To make it short: This is one of the reasons why my company dumped its Jira enterprise license and turned to another solution.

we created a custom field for our customers. Now it would be important to be able to 'quick search' for the customer name witrhout scrololing down the whole custom fields....

I'm now on company #3 (see prior comments) where I am trying to get JIRA spread to the business teams and this is a problem for them. We have a business-related entity (Tower Id) that is a custom JIRA field, and I keep getting bug reports like "JIRA Search is broken" and have to patiently explain that the custom field can't be searched via quick search (only by using Search For Issues and awkwardly scrollllllllllllling way down past a bunch of other stuff).

What's worse for them is that I told them to always put TowerId as part of the summary as a workaround (in addition to putting it in the custom field). That seems good on the surface but it actually makes it worse, because then some user forgets and the ticket gets "lost". Example: Users dutifully place TowerId in the summary for 9 tickets. Search finds them. A 10th user creates a ticket but forgets to put towerid in the summary, although they put it in the custom field. The assignee team searches and finds 9 tickets instead of 10. They are getting enough hits that it seems to we working, but the 10th ticket ends up "lost" until someone gets around to browsing the project or analyzing their dashboards.

We would really, really like this feature.

I will be away on vacation until 10th.
For any urgent issues, please contact to Hosang Lim(hslim@inustech.com).

Thanks,
Heewook
.

I will be away on vacation until 10th.
For any urgent issues, please contact to Hosang Lim(hslim@inustech.com).

Thanks,
Heewook
.

I will be away on vacation until 10th.
For any urgent issues, please contact to Hosang Lim(hslim@inustech.com).

Thanks,
Heewook
.

I will be away on vacation until 10th.
For any urgent issues, please contact to Hosang Lim(hslim@inustech.com).

Thanks,
Heewook
.

I will be away on vacation until 10th.
For any urgent issues, please contact to Hosang Lim(hslim@inustech.com).

Thanks,
Heewook
.

I will be away on vacation until 10th.
For any urgent issues, please contact to Hosang Lim(hslim@inustech.com).

Thanks,
Heewook
.

I will be away on vacation until 10th.
For any urgent issues, please contact to Hosang Lim(hslim@inustech.com).

Thanks,
Heewook
.

I will be away on vacation until 10th.
For any urgent issues, please contact to Hosang Lim(hslim@inustech.com).

Thanks,
Heewook
.

I will be away on vacation until 10th.
For any urgent issues, please contact to Hosang Lim(hslim@inustech.com).

Thanks,
Heewook
.

I will be away on vacation until 10th.
For any urgent issues, please contact to Hosang Lim(hslim@inustech.com).

Thanks,
Heewook
.

I will be away on vacation until 10th.
For any urgent issues, please contact to Hosang Lim(hslim@inustech.com).

Thanks,
Heewook
.

I will be away on vacation until 10th.
For any urgent issues, please contact to Hosang Lim(hslim@inustech.com).

Thanks,
Heewook
.

I will be away on vacation until 10th.
For any urgent issues, please contact to Hosang Lim(hslim@inustech.com).

Thanks,
Heewook
.

I will be away on vacation until 10th.
For any urgent issues, please contact to Hosang Lim(hslim@inustech.com).

Thanks,
Heewook
.

I will be away on vacation until 10th.
For any urgent issues, please contact to Hosang Lim(hslim@inustech.com).

Thanks,
Heewook
.

I will be away on vacation until 10th.
For any urgent issues, please contact to Hosang Lim(hslim@inustech.com).

Thanks,
Heewook
.