Currently, the only way to access the resolved_at field from the /tickets endpoint is by passing in an include query param, /tickets?include=stats .
For a customer’s use-case we’d like to switch from using /tickets to /search/tickets but when testing for /search/tickets/{query}?include=stats this caused an error. There currently isn’t a way to get resolved_at from /search/tickets.
Could support be added to include this field or a way to access ?include= fields from the /search/tickets endpoint to keep it consistent?
