Store geo on ticket at creation, drop GeoLite reads

PerformanceMediaService
Shipped
25 Aprili 2026, 23:25 UTC
Author
Kamo
Commit
10f70de

**************** now captures the visitor's geo once (via GeoLookupService) and persists ip/country/city/subdivision on the SupportTicket itself. SupportTicketService.toDTO reads geo straight off the ticket — no live GeoLite range scan, no visitor-table fallback for geo (visitor is still loaded for the latest displayName, in bulk for the list endpoint). Legacy tickets without the snapshot fall back to visitor.countryCode.

All changes

Je, unaona nini kuhusu usafiri?

Kila moja ya hizi updates ardhi katika nafasi yako ya kazi moja kwa moja. Kuanza bure na kuangalia kukua wiki baada ya wiki.

Kuwa Huru MileleMtazamo wa bei