Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Search in queue does not find text in requests custom fields

Jochen Betz May 13, 2024

Using normal filters and filter for the service management project I can use the search box to find issues which contain a specific text in custom fields.

Using the queue view of the service management project with the same search text leads to no results.

It seems either the queue view/search does not check custom fields or it is an issue with the service management project type.

Anybody can reproduce this? Or even better has a solution?

2 answers

1 accepted

2 votes
Answer accepted
Rebekka Heilmann _viadee_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 13, 2024

Hi @Jochen Betz 

can you provide some more details on the Search request, for instance post the JQLs for the "normal" issue search and the Queue? What field types are those custom fields?

Jochen Betz May 13, 2024

Hello @Rebekka Heilmann _viadee_ , sure. Please find more details below. Let me know if you need more details.

The search request uses only the basic search as provided in the queue view.
The text in this case is an a custom field of type "Text Field (multi-line).

2024-05-13_11-22-54.png

Via Filter/All Issues brings up the expected result:
2024-05-13_11-21-14.png

 

When choosing the path via the queue, the search for the same text, result is empty:

2024-05-13_11-21-50.png

 

Rebekka Heilmann _viadee_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 13, 2024

So these are two very different functionalities.

In issue search, the "free text" search equals the JQL

text ~ Gutteil

That searches the Summary, description and comments for that text.

 

In the queues, it's not JQL. It's rather like a Strg + F search. So if that text doesn't appear right in the Queue view (in the fields the Queue is showing), you won't find the issue.

In Queues you can make use of the JQL in the Queue's query, but i assume the search word is different everyone. So not really helpful in your case. 

Jochen Betz May 13, 2024

Thank you @Rebekka Heilmann _viadee_  for the clarification. It's very confusing to have this behavior as it is not a tiny bit obvious to the user. But even more: Why is "search" here implemented yet another time and not used the as in other places?
Can this be configured?

Rebekka Heilmann _viadee_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 13, 2024

No, this cannot be configured.

Like I said - the JQL search for Queues exists but is "hidden" in its configuration. So you'd need to edit the Queue to add the text filter.
tbh, I've never thought much about it and thought it fairly logical but then on the other hand I tend to only configure the projects and not work in them as an Agent.

Jochen Betz May 13, 2024

Yes that's often the problem: Developers of a tool don't use it as "customers" but provide what they think is useful (for them). Not excluding myself from this habit though.


In this case, the agents only work on the queues without even much knowledge about all the other menus and features if Jira - and should not need to know.

As you where guessing correct: The search term is always something different... that's why it is a search.

0 votes
Hannes Obweger - JXL for Jira
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
May 13, 2024

Hi @Jochen Betz

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.

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 any custom fields.

This is how it looks in action:

queue-search-for-reporter.gif

(I'm using the reporter field here, but it would work with any other field as well.)

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

Jochen Betz May 13, 2024

Thank you @Hannes Obweger - JXL for Jira , but I expect a consistent workflow in Jira itself.

To me it sounds like a horrible waste of resources that developers are re-inventing the wheel over and over again. I would not be surprised to see this to be the case also this time, albeit so far I hope it's my mistake.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events