Re-creation of index-pattern broke all related saved objects

[smerzlyakov]

Kibana version: 7.2.0

**Elasticsearch version:**7.2.0
Server OS version: Centos 7
**Browser version:**Firefox
Browser OS version: Mac

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

Describe the bug:
I have dasboards, that use "winlogbeat-" index-pattern and than i delete that index-pattern (during trying fixing a problem). And that create it again. Now all my dashboards and visualisations are broken.
"Could not locate that index-pattern (id: winlogbeat-), [click here to re-create it]" but this index-pattern exist!
Steps to reproduce:

1. Delete index-pattern
2. Create index pattern
3. Your Saved objects are broken. Even built-in.

Expected behavior:
All saved objects, that uses name of index-pattern and not ID continue to work after re-creation of index-pattern.
Screenshots (if relevant):

Errors in browser console (if relevant):

Provide logs and/or server output (if relevant):

Any additional context:
Where does IDs hardcodes??If i open any of saved object in kibana i see only references by "winlogbeat-*" and no ID!

[elasticmachine]

Pinging @elastic/kibana-app

[azasypkin]

Where does IDs hardcodes??If i open any of saved object in kibana i see only references by "winlogbeat-*" and no ID!

When you open new index pattern, you should see it's ID in the URL, no? But nevertheless we'd like to make it more intuitive and less confusing here, here and here.

Having said it doesn't sound like a bug in Kibana, and Discuss post you've already created suits better for things like this, let's continue discussion there.

[smerzlyakov]

I do not understand why it is not a bug?

1. Kibana says that there is no index pattern "winlogbeat-*"
2. Index-pattern exist and you can't create it.

[smerzlyakov]

Ok, as i see in last thread - it is still under discussion.