Opened 13 years ago

Last modified 11 years ago

#3026 new enhancement

Time filter only cuts off the end of the list instead of offering disjunct time spans

Reported by: sascha_silbe Owned by:
Priority: Unspecified by Maintainer Milestone: Unspecified
Component: Sugar Version: Unspecified
Severity: Minor Keywords: design
Cc: garycmartin Distribution/OS:
Bug Status: Unconfirmed


The time filter in the Journal only changes the number of entries shown; it doesn't select different sets. With the default setting of showing everything, the data store will already need to scan the entire index, so the performance advantage of changing the setting manually is usually negligible.

While the current time filter options may be useful in combination with sort orders other than the default time based one, it makes sense to additionally offer time spans (start and end time limited) and / or starting times (open ended) for the time filter.

We should also provide a way to search for arbitrary time spans by using Xapian value ranges in the text search field, similar to how we already support searching for certain other metadata. But let’s open another ticket for that.

Change History (4)

comment:1 Changed 13 years ago by sascha_silbe

  • Cc garycmartin added
  • Keywords design added

comment:2 Changed 13 years ago by walter

For what it is worth, the original idea was to have a filter that changed two parameters at once: the time window and the date, so that as you moved back in time, the window increased. e.g., right now, you'd get 24 hours; yesterday, you'd get 48 hours; a week ago, you'd get 7 days; a month a go, you'd get 28 days, etc. with the interval centered on the date. Imagine a continuous slider with interval bars that widen as it moves in one direction and narrow as it moves in the other. Not sure how to do this with a combo box.

comment:3 Changed 11 years ago by dnarvaez

  • Component changed from journal to sugar

comment:4 Changed 11 years ago by dnarvaez

  • Bug Status changed from New to Unconfirmed
Note: See TracTickets for help on using tickets.