[Discover] Invalid state of alert flyout on initialization

[ghudgins]

Kibana version: 8.3

Elasticsearch version: 8.3

Server OS version: Linux / Elastic Cloud

Browser version: Chromium Edge v100

Browser OS version: OSX

Original install method (e.g. download page, yum, from source, etc.): Elastic Cloud

Describe the bug:
Invalid state when entering alert flyout which causes a subtle negative experience without the user having done anything 'wrong'

Steps to reproduce:

1. In discover, enter a search term "orphaned pod"
2. Deciding this is a good alert, click Alerts -> "Create search threshold rule"

Result: Red error state around the name

Expected behavior:

• If name is omitted, error state on name field shouldn't show until the user attempts to submit
• Alternative: default name could resolve this too {search term} threshold alert like orphaned pod threshold alert in the above example

Screenshots (if relevant):
Initial screen state:

[elasticmachine]

Pinging @elastic/kibana-data-discovery (Team:DataDiscovery)

[kertal]

• Alternative: default name could resolve this too {search term} threshold alert like orphaned pod threshold alert in the above example

this is what we can do in Discover, since validation of the form is I think domain of @elastic/response-ops . However due to the potential complexity of our query and filters, I'd suggest something like:

New threshold alert rule

[kertal]

removing the bug label since it's not a technical bug

[kertal]

Closing this because it's not planned to be resolved in the foreseeable future. It will be tracked in our Icebox and will be re-opened if our priorities change. Feel free to re-open if you think it should be melted sooner.