Conditions not working as expected for m2o fields

[MarkoMestrovicShape]

Preflight Checklist

• I have completed all Troubleshooting Steps.
• I'm on the latest version of Directus.
• There's no other issue that already describes my problem.

Describe the Bug

Setting condition rule with a relational field, such as:
collectionO->key equals 3 doesn't work consistently.

To Reproduce

Create two collections. Give them m2o relationship. In the M collection choose one field and give it condition that includes checking value of O field.

For example:

collection_M->key equals KEY_VALUE

Checkbox the Hidden on Detail option.

The field never becomes hidden no matter which O field is selected.

Errors Shown

None

What version of Directus are you using?

v9.4.3

What version of Node.js are you using?

v14.5.0

What database are you using?

Postgres 13

What browser are you using?

Chrome

What operating system are you using?

Windows

How are you deploying Directus?

Docker

[Oreilles]

Closing as duplicate of #8228