Description
Custom reference field set as dependent only applies the expected filter if set to suggestion reference type. When set to dropdown reference, the dependency fails and the dropdown list always shows every value present.
Steps to Reproduce
1 - Open an Incident form to configure its layout
2 - Create a new reference field, "Service/Module" to the CMDB Configuration Items table:
[task.business_service]
mandatory with default value
simple ref qual
Dropdown reference to Business Services [cmdb_ci_service]
3 - Create a new reference field "Sub Module" to the CMDB Configuration Items table:
[incident.u_sub_module]
mandatory with default value
simple ref qual
Suggestion reference to Business Services [cmdb_ci_service]
Dependent on "Service/Module"
4 - When changing the "Service/Module" value, and then typing something into "Sub Module", observe the dependency works and the suggestions are correct for the selected Service/Module.
5 - Change the "Sub Module" field to Dropdown reference.
6 - Observe the dependency stops working, the dropdown field always shows every value, regardless of the value in "Service/Module". Applying default filter "parent is not empty" or clearing instance cache doesn't change the behaviour.
Workaround
After carefully considering the severity and frequency of the issue, and the cost and risk of attempting a fix, it has been decided to not address this issue in any current or near future releases. We do not make this decision lightly, and we apologize for any inconvenience.
As a workaround, please use Suggestion Reference dependent fields instead of Dropdown Reference.
Related Problem: PRB758180