they look absolutely fine and they should give you the desired result.
However, on reading the documentation, I noticed this, quoting it here:
If you’re not getting a result for the above query, there’s a chance that the field might have been created recently or it has been moved to a new infrastructure. To query on these custom fields, use ‘custom_string’ instead of the actual field label.
Yes @ManiDeepak_Vandrangi, I tried the results are coming. but also I found a drawback in this query. If another ticket, another custom field(other than id number and policy number fields) also has the same value(7894) then we won’t get actual id number or policy number filter tickets right?