[Index Patterns] Conflicting fields no longer show matching indices

[TheRiffRafi]

Kibana version: 7.15.0

Elasticsearch version: 7.15.0

Describe the bug:
This was requested back in: #45135
It looks like it was implemented as it was working on 7.12.1:

And now looking at 7.15 we see that conflicting indices are no longer showing up:

Expected behavior:
Clicking on field should show conflicting indices.

[cjcenizal]

@elastic/kibana-app-services Looks like you’re not getting pinged when your labels are added to issues any more.

[mattkime]

closing in favor of #113061

[VimCommando]

closing in favor of #113061

In the meantime, how am I supposed to identify the indices and impacted fields if I'm running a version where conflict fields are not clearly identified? Since 7.16 is already out, it is going to be run for a very long time.

[lucabelluccini]

It's a really ugly workaround, but...

Use the API (or inspect the page via the browser dev tools / network tab):

https://YOUR KIBANA URL WITH PORT/api/index_patterns/_fields_for_wildcard?pattern=INDEXPATTERN&meta_fields=_id&meta_fields=_type&meta_fields=_index&meta_fields=_score&meta_fields=_source
Where INDEXPATTERN must be escaped for : in case of CCS patterns (e.g. for *:myindices use *%3Amyindices).

If a field is in conflict, the type is conflict and you have a conflictDescriptions with the list of indices.

Another method is to open the browser network inspector and access the Index Pattern page, then select the index pattern for which we want to know the conflicts. In the response you'll get the whole JSON representation of the fields and look for conflict.

---

Please note this has been addressed in #113061