[Fleet]: No error popups for incomplete queries entered in search box on Agent Policies and Enrollment tokens tab.

[amolnater-qasource]

Kibana version: 7.14.0 BC-3 Kibana cloud environment

Host OS and Browser version: All, All

Build details:

Build: 42545
Commit c314921a9893e0b46d9a3958f5520e3d6b1ce7d5

Preconditions:

1. 7.14.0 BC-3 Kibana cloud environment should be available.

Steps to reproduce:

1. Login to Kibana environment.
2. Navigate to Agents tab and enter any incomplete search query say agent id:
3. Observe Error popups for incomplete query.
4. Navigate to Policies tab and enter any incomplete search query say ingest-agent-policies.name :
5. Observe no error popups for incomplete query on Agent Policies tab.

Note:

• This issue is also observed on Enrollment Tokens and Security> Endpoints tab.

Expected Result:
Error popups should be displayed for incomplete queries entered in search box on Agent Policies tab.

Screenshot:

What's working fine?:

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[amolnater-qasource]

@manishgupta-qasource Please review.

[manishgupta-qasource]

Reviewed & Assigned to @jen-huang

CC: @EricDavisX

[jen-huang]

Feels like this could be related to #106197.

[hop-dev]

I think it is @jen-huang. Though at the moment turning on the errors would error for some queries I think are valid, I'll pick this up once I get a steer on #106197

[hop-dev]

@jen-huang I believe we suppress errors at the moment because we run the search on every change to the search term, there is a bit of a difference in how we search in the different fleet tabs:

• agents & data streams: search only when ⏎ is pressed, show syntax errors
• agent policies & enrolment tokens: search on every change to the search input, suppress errors

My instinct would be to move all to only searching on ⏎ and displaying errors if there are any. What do you think?

[hop-dev]

After speaking to @nchaulet and @kpollich about this, I have created a separate issue to normalise the search behaviour across the fleet tabs #107546, I am happy to keep this open in the meantime.

[jen-huang]

I'm going to close this in favor of #107546, as resolving that will provide a general solution/UX pattern across our search UIs.