Problem
Searching for relations and tickets currently only works on a limited set of fields. If you don't have the exact name or ticket number, there is often no way to find what you're looking for. For example, a phone number cannot be used as a search term (even though it's stored on the relation or linked to other tickets) so an incoming call from an unrecognised number can't be traced back to a relation or an open ticket.
Impact
This costs time in day-to-day work and makes some lookups impossible rather than just slow. It comes up most often when the only identifying detail available is something other than a name: a phone number, an email address, an address, or a fragment of text from the ticket itself.
Requested improvement
Enable full content search (like elastic search) across relations and tickets, so that any stored field (including phone numbers, email addresses, addresses, and free-text fields such as descriptions and notes) can be used as a search term. Ideally partial matches would work too, so a search on the last six digits of a phone number still returns the right relation.