-
Suggestion
-
Resolution: Fixed
-
15
-
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Hi everyone,
Thanks so much for your votes and comments on this issue.
As most of you have seen in the comments below, this issue is resolved in JIRA 5.2!
In addition to making issue search and issue navigation faster and easier to use, text custom fields are now a part of all quick search and simple search text searches.
Thanks for your patience and we hope you appreciate our open approach to feature requests.
Cheers,
Bryan
JIRA Product Management
brollins at atlassian dot com
Original Description
Currently to search for text in a custom field you need edit the search for each field separately. It would be useful if you could add the custom field to the main text query search, like what is done with comments and environment.
- is duplicated by
-
- Closed
- is related to
-
- Closed
- relates to
-
- Closed
- was cloned as
-
- Closed
-
- Gathering Interest
[JRACLOUD-7686] Allow text custom fields to be searched from quick search / text search.
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
Eva
added a comment - 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.
Eva
added a comment - 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.
Guillaume Côté
added a comment - 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.
Guillaume Côté
added a comment - 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. 
Scott Morris
added a comment - 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.
John Price
added a comment - 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.
John Price
added a comment - 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. 
Amul Shah
added a comment - 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. 
Amul Shah
added a comment - 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. 
Mikael Hagberg
added a comment - I just want it to work, the solution behind i personaly don't care about.
Mikael Hagberg
added a comment - I just want it to work, the solution behind i personaly don't care about.
Thanks Roy, Nick and the rest of the team who worked on this! I will have some happy campers here.
Cheers