Jira SM search bar- not checking the reporter field?
Asked by Ross E_ Snyder:

Noticed that the "search" in the navigation bar (this one) ![searc.png](https://community.atlassian.com/t5/image/serverpage/image-id/331139i319BB4D80774ABEC/image-dimensions/1818x80?v=v2 "searc.png")  
in Jira Service Management Cloud doesn't check the reporter field when you search. So if I search "John Smith", I only see tickets where "John Smith" is written in the subject or description fields. Is that intended behavior? Is it something we can change?  

I'm aware that "correct" way to search would be via JQL or the "Basic" GUI, but that's inconvenient enough that most of our agents just end up adding the name of the reporter to the subject or description instead.


Answers:
author: Ezgi Bay?nd?r
body: Hey [@Ross E_ Snyder](/t5/user/viewprofilepage/user-id/5013773) ,

Unfortuntely there is no default option to customize search bar options. You can only search with keywords in this bar.


author: Joseph Chung Yin
body: [@Ross E_ Snyder](/t5/user/viewprofilepage/user-id/5013773) -

Welcome to the community. One more thing to note is if you are familiar with using JQL syntax to create your search, then you can use the "Filters" menu option and then create your custom searches on different fields (i.e. Reporter field etc...

Depends on where you are via the project UI, you can just click on "Advanced issue search" at the bottom to access the same UI under "Filters" menu \>\> View all issues to generate your custom searches (Basic mode or JQL mode)

Example -

![2024-06-21_16-26-28.png](https://community.atlassian.com/t5/image/serverpage/image-id/331205iB8B635783A7BFC82/image-size/large?v=v2&px=999 "2024-06-21_16-26-28.png")

Hope this also helps.

Best, Joseph Chung Yin


author: Hannes Obweger - JXL for Jira
body: Hi [@Ross E_ Snyder](/t5/user/viewprofilepage/user-id/5013773),

welcome to the community!

to the best of my knowledge, the search within queues is relatively limited. It appears like it might primarily (only?) be considering an issue's *summary*, but I'm not 100% sure.

I don't know if this problem justifies additional tooling for you, but just to put it out there: If you're open to solutions from the Atlassian Marketplace, you may want to have a look at the app that my team and I are working on, [JXL for Jira](https://marketplace.atlassian.com/apps/1224710?hosting=cloud&tab=overview&utm_source=atlassian-community&utm_medium=referral&utm_content=2733510).

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields - including all JSM-specific fields - much like you'd do in e.g. Excel or Google Sheets. It also comes with a number of advanced features, including support for (configurable) *issue hierarchies* , *issue grouping* by any issue field(s), *sum-ups* , or *conditional formatting*.

Plus, its sheet search considers all visible fields, including the reporter.

This is how it looks in action:

![queue-search-for-reporter.gif](https://community.atlassian.com/t5/image/serverpage/image-id/314593i744C55ACD3E9B7B6/image-size/large?v=v2&px=999 "queue-search-for-reporter.gif")

As every sheet in JXL is powered by a JQL statement or filter, you can easily model your queues as JXL sheets. It also allows cross-project queues, if that's something you'd be interested in.

Any questions just let me know,

Best,

Hannes


Tags: cloud

jira-service-management

jira-service-management-cloud