New request
#19026: Deactivating Relations does not Prevent the use of that Relation
We'll provision a sandbox, run an agent against the issue, and open a draft PR. You can pull the branch and iterate from there.
Bug Description
If a Relation is Disabled, for example disabeling the Notes Relation on People. Notes can still be selected for people, and added There and Notes can also still be assigned to People. (This appers to apply to all Relations, althoug i did not check all options)
Notes on People disabled: <img width="1134" height="761" alt="Image" src="https://github.com/user-attachments/assets/0d55662f-f19e-4b33-870c-e5ecaea875fe" />
Notes still availible on People Object: <img width="784" height="1089" alt="Image" src="https://github.com/user-attachments/assets/001210b6-f992-4bd9-b3d2-13fb7e680421" />
Notes can be assigned to People: <img width="514" height="352" alt="Image" src="https://github.com/user-attachments/assets/29989745-946e-42fd-b4ce-043daf4b1902" />
Expected behavior
The expected Behavior is that the option to add a Note would not be shown on a People Object. Addidationally the option to assign a Note to a Person should not be availible (Persons should not be selectable).
This behavior was last observed by me in the version 1.15 (I also observed this issue in 1.18, I did not check other versions)
The frontend ignores the disabled state of relations and continues to show relation pickers and assignment options that should be hidden.
- packages/twenty-front/src/modules/object-record/record-field/ui/meta-types/hooks
- packages/twenty-front/src/modules/object-record/hooks
- packages/twenty-front/src/modules/views/components
- packages/twenty-server/src/engine/metadata-modules/flat-field-metadata/utils