Filter doesn't work on Data Streams page for Non-default namespace with special characters.

[amolnater-qasource]

Kibana version: 7.13.0 Snapshot Kibana Cloud environment

Host OS and Browser version: All, All

Build Details:

   Artifact link used: https://snapshots.elastic.co/7.13.0-90ede9b6/downloads/beats/elastic-agent/elastic-agent-7.13.0-SNAPSHOT-windows-x86_64.zip
   Build: 39868
   Commit: 7977d493ce4fedd35b9c79435be4b6c2c6559345

Preconditions:

1. 7.13.0 Snapshot Kibana Cloud environment should be available.
2. Agent must be enrolled with default policy having System integration.

Steps to reproduce:

1. Login to Kibana environment.
2. Navigate to Policies tab and create few policies with namespace having special characters like $,^,+,@
3. Navigate to Agents tab and assign to each policy
4. Navigate to Data Streams tab and apply namespace filter.
5. Observe filter doesn't work and shows red line under search bar.

Expected Result:
Filter should work for non-default namespace with special characters or User should not be able to create policy with these special characters $,^,+,@

Reference Tickets:
elastic/beats#23352

Screenshots:

[amolnater-qasource]

@manishgupta-qasource Please review.

[manishgupta-qasource]

Reviewed & Assigned to @dedemorton

[elasticmachine]

Pinging @elastic/fleet (Feature:Fleet)

[jen-huang]

This isn't a super critical issue IMO. We need to wrap the query. Unassigning myself so anyone can pick this up.

[EricDavisX]

sounds good, thank you. @ph @mostlyjason we can explicitly scope it for 7.14 or beyond, or leave it unassigned in case anyone wants to pick it up ad-hoc

[mostlyjason]

Looks like these are valid index name characters https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-create-index.html#indices-create-api-path-params

Agree on not high impact since custom namespaces are an advanced feature so a small portion of people will run into this

[jen-huang]

Closing as a duplicate of #87036.

[dikshachauhan-qasource]

Bug Conversion

• 01 new testcase is created under the 'Data streams' section:
  • https://elastic.testrail.io/index.php?/cases/view/147360

Thanks!