Valid intersections not working as expected (account / movement combination)

Summary:

When creating a "valid intersection" on account / movement and using a "shared movement member", other shared versions of that same movement member will NOT become valid. Only when selecting the Stored version of that movement, all shared versions of that movement will become valid.

This is not how I would expect it to work. This is an issue because we created movement groups for different balance sheet accounts in which we re-use movement members (like "Reclassification"). These movement groups are then used in the valid intersection setup.

In these movement groups we are only using "shared" versions of the movements, thus creating this issue. The problem is that when you for example create a journal entry, you must select the correct "shared" version of that movement to be able to record the entry.