https://www.zabbix.com/documentation/7.0/en/manual/discovery/low_level_discovery#override

I'm talking specifically about Operations for the overrides. Even more specifically - about Value for it.
Here I'm indicating what I'm talking about:

It's quite unclear how it's actually working. I had this impression myself and heard this from a few users.

In the doc we have very short description for "Condition -> Pattern" field. This description is not clear actually. What filed of an object its dedicated for?
The example screenshot helps us to assume that filtering is based of object name. This is helpful, but this is in doc only and still not fully clear.

So, to make it much more clear I see a few point to be done:

1. We should state that it's based on "Object name" property. Because without looking on doc example you may assume, for example, an item key or trigger expression etc.
2. Analyzed name is taken *after *expanding LLD macros, i.e. the object name how it's seen in configuration section after being discovered.

Ideally, the Frontend should indicate that it's actually based on object Name.
It could be implemented by renaming "Condition" to "Name condition" or adding a pop-up "?" icon next to "Condition" to give an advise what property is expected.

Actually I'd vote for both changes - naming in code and doc.