Last modified: 2014-08-05 08:22:27 UTC
as an analyst, I can set the start & end dates to visualize, so I focus the visualization on a narrow period of time.
Team discussion on points: Filtering may happen at client Can be a naive filtering. Performance is secondary. If the performance is bad, we can add another card to improve performance. We need to implement a custom control for time selection NOTE: the high point value is mostly due to the fact that we're implementing a new custom time selection control. Changing what is possible to select would not make the filtering easier, but choosing a simple (calendar-only for example) control would simplify things. Filtering by itself, with an out of the box calendar-only time selection would cost: 13 points
> Performance is secondary. >If the performance is bad, we can add another card to improve performance. Sorry, but if filtering is done client side (the only way it can be done giving our current access to data) performance cannot be bad. We are just repainting as all data is already loaded into memory. If performance is bad on that scenario indicates a problem with painting, problem that we would have in the vanilla use case of painting data not filtered.
