Correctly Identifying Empty Fields in 'Null' Filters

In the ticket filter option, selecting any property value as 'null' does not mean that the specific property exists as empty or that the user has not populated that property. For example, if I have a ticket with a dropdown property ‘x’ left unfilled, filtering the tickets by selecting the ‘null’ value for this field will not display this ticket.

Currently, in the filter condition, 'null' means that a user must deliberately select an empty value from the dropdown for it to show up in the filtering results. This should be corrected so that the filtering can be done for Empty fields as well.