Stories retrieved via the api should have a last change timestamp
I'm working on a tool that uses the api data to store a local cache of the stories. Instead of retrieving and storing all the stories all the time, I'd like to be a little more intelligent and only update locally the stories that have changed.
To do so now I would need to compare every story locally with the story I obtain via the API and only update the ones that changed.
At the very least the API could supply a "last-changed-at" time stamp which I could store and use to update only the changed stories. Ideally we'd have access to a last-changed-at time stamp and to the history of the story, so that I don't have to compute the changes myself.
Thank you
To do so now I would need to compare every story locally with the story I obtain via the API and only update the ones that changed.
At the very least the API could supply a "last-changed-at" time stamp which I could store and use to update only the changed stories. Ideally we'd have access to a last-changed-at time stamp and to the history of the story, so that I don't have to compute the changes myself.
Thank you
3
people like this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
-
Inappropriate?It would also be important to be able to sort and (esp.) filter by the last-changed-at story attribute.
E.g. during an integration run, you'd want to fetch stories that have been modified since the last integration run (e.g. last-changed-at > last-time-run).
1 person thinks
this is one of the best points
-
Inappropriate?Oh yeah! Without this performing a sync via the API with another system is next to impossible...
Loading Profile...



