Closed jnaviask closed 4 days ago
we need to support version history on the model as well
I think we have this already. In Threads and Comments we have version history which looks to have the complete history. We should just display this I think. For this reason I think it is about a 2 in points (main changes will be on the front end), but if I hit snags I will report back and bump up the points.
versioning logic was broken and needed fixing, bumping 1 point
Bumping down to 1 because of misunderstanding. This ticket was only the backend changes not front end
Description
7558 defines the product goals + UI items for version history support, but we need to support version history on the model as well. We should determine what changes to the model and routes (if any) will be needed to support version history on the client side. We should aim for a simple implementation which we can add complexity to as needed, if we see degraded database performance. Please discuss with @Rotorsoft (and the rest of platform team) and feel free to produce a formal specification of the changes involved.