Might be connected to Version History to Playback Space. I started storing recent operations in the db , and there’s an API route for listing recent history steps on a space. That said it’s a challenge to figure out how to expose it.
Would having a list of api operations eg userA moved cardB, userC deleted cardV,…
If so, what kind of granularity would be helpful to see? Eg
- userA moved cardB
- userA moved cardB to position xyz, at specific time. Which caused connection path id X to update.
Some of the operations like bulk updating multiple items at could create some super long entries.
The easiest thing would be to expose the raw json operations , but it would probably be very hard to human parse