updatedAt field always equals createdAt in API v2

Environment:

• API Endpoint: https://do.featurebase.app/v2/posts

• Method: GET /v2/posts

• Sample Size: 1000+ tickets analyzed

• Workspace: visszajelzes.drr.hu

Issue: The updatedAt field in the API response always returns the exact same timestamp as createdAt, even for tickets that have been modified, commented on, or had their status changed to "completed" or "canceled".

Evidence:

• Analyzed 694 completed tickets

• 100% of them have createdAt === updatedAt

• Example:

json

 {  "status": { "type": "completed" },  "createdAt": "2026-01-26T14:34:40.848Z",  "updatedAt": "2026-01-26T14:34:40.848Z" // Same timestamp!  }

Missing Fields: The API response does NOT include:

• ❌ completedAt - when ticket was marked as completed

• ❌ statusChangedAt - when status last changed

• ❌ closedAt - when ticket was closed

Impact:

• Cannot calculate MTTR (Mean Time To Resolution)

• Cannot track when tickets were actually closed

• Cannot identify recently updated vs. recently created tickets

Request: Please either:

1. Fix updatedAt to reflect actual last modification time, OR

2. Add completedAt field for when status changed to completed/canceled, OR

3. Add statusChangedAt field for any status changes

Urgency: This blocks critical business metrics