core
core copied to clipboard
dotCMS
Relationships are not respecting changes to requiredness
Describe the bug When you change the existing required state of a relationship, the requiredness does not change functionally. It correctly displays the checkbox based on your selection, but when actually managing relationships it does not respect the state of the checkbox.
Reproduced on: 22.03/22.06
To Reproduce
- Create a relationship between two content types, set it to required
- Attempt to create a contentlet without specifying a related content
- Save, you will correctly get an error stating the relationship is required
- Change the relationship to Not Required (unchecked)
- Reopen the relationship, the required checkbox will remain unchecked
- Attempt to create a contentlet without specifying a related content
- Save, you will no incorrectly still receive the error stating a relationship is required
Acceptance Criteria You should be able to change the requiredness of a relationship
Another customer hitting this: https://dotcms.zendesk.com/agent/tickets/108057
looking at this seems like the verification of requiredness happens in the BE and for some reason the changes in the CT model is not updated
Hey team! Please add your planning poker estimate with Zenhub @hmoreras @jcastro-dotcms @jdotcms @rjvelazco
IQA Status: Unable to Reproduce
I confirmed with @bryanboza that this issue is not reproducible with the provided steps to reproduce in the latest stable dotCMS 22.10 Docker image. Creating a required Relationships field in a Content Type and then removing such a status is not causing the required message to keep showing up.
