Hello! I’m currently running into an issue where we’re switching from using the /tickets endpoint to the /search/tickets?query=[query] endpoint. We were previously using the stats.resolved_at field to populate when a ticket was marked as resolved but it seems like we aren’t able to access that field from /search/tickets.
I know for /tickets we could do include=stats to access the resolved_at field but when trying to apply the same logic to the /search/tickets endpoint, it errored. Does anyone know of another way to access the resolved_at field from the search endpoint? Seems like a very important field to be missing from the Ticket object.