JQL "text" keyword

[MattS]

Does JQL such as "text ~ foo" really search all custom fields of type Text?

I thought it only searched Summary, Description and Comments but https://confluence.atlassian.com/display/JIRA/Advanced+Searching#AdvancedSearching-Text suggests it searches the custom fields too. That might explain why some searches are so slow when I'm in a JIRA with 1000 text fields!

Has anyone else had problems with slow queries when using "text ~"?

[Boris Berenberg · Accepted solution]

text does search custom fields. It will also search third party custom fields with appropriately configured searchers as well I believe. 

[MattS]

Hmm. That could well be slow for large instances!

[Boris Berenberg]

It is intended as an extremely broad search, if you know exactly what fields you are looking in, then you can expect much better performance.

[MattS]

I've updated the docs at https://confluence.atlassian.com/display/JIRA/Advanced+Searching#AdvancedSearching-textPerformingTextSearches with that good advice

[Danny Hendargo]

@Boris Berenberg , Entering <string> into the Quick Search box is equivalent to "text ~ <string>" and used to be expanded to "summary ~ <string> or description ~ <string> or comment ~ <string>". Can we have that back In JIRA 6.2.7? That is, to configure JIRA to not search for all customfields but a few. We have 848 custom fields and the Quick Search is not quick but resulting in proxy error, or JIRA's saying "No results were found". In other words, text search through Quick Search box is unusable. Reducing the number of custom fields in the instance is not an option. We need a way to constrain the Quick Search to search a list fields and not all fields. This way, the regular non-power users can search without being bitten by the slow unreliable search.

[Boris Berenberg]

I filed a request for this at: https://jira.atlassian.com/browse/JRA-42162

[Paul Pasler]

If you have performance issues, you could think about reducing you custom fields.