Opened 18 years ago
Last modified 7 years ago
#4834 new enhancement
Default "from" date in Timeline
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | unscheduled |
Component: | timeline | Version: | devel |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
The default "from" date in the TimeLine is today.
Could we make it the day of the last event?
thanks.
Attachments (0)
Change History (7)
follow-up: 2 comment:1 by , 18 years ago
follow-up: 3 comment:2 by , 18 years ago
Replying to cboos:
I guess the current default is only problematic when there are no events to be displayed.
that's right. we have a high-traffic project, which has "daysback" set to 0 (to show only one day) but depending on circumstances (e.g. weekend etc) there is sometmes nothing for a couple of days. in which cases you have to either click yourself through to the last events or increase the daysback manually, which kinda means to do "lots of clicks"
In this case, we could probably iterate back, period by period, until events are found. Would that be OK?
What the best way of implementing such a feature is, I don't know. For svn events one certainly could pull the newest revision and take its date. I don't know about tickets and wiki if it is possible to ask for the "most recent" event in that area and ask for its date. But that would probably be better than iterating back.
comment:3 by , 18 years ago
Milestone: | → 0.12 |
---|
Replying to Sergei Haller <sergei@sergei-haller.de>:
Replying to cboos:
In this case, we could probably iterate back, period by period, until events are found. Would that be OK?
… I don't know about tickets and wiki if it is possible to ask for the "most recent" event in that area and ask for its date.
No it's not currently possible.
But that would probably be better than iterating back.
Iterating back would simply imply to do several queries until there's one which return results. I don't think the queries returning no results will have a big performance cost, unless perhaps the period is 1 and we need to go months back. If this proves to be a problem, we could increase progressively the period span using some simple heuristic.
comment:5 by , 14 years ago
Milestone: | next-major-0.1X → unscheduled |
---|
comment:6 by , 10 years ago
Owner: | removed |
---|
comment:7 by , 7 years ago
#8701 closed as a duplicate, requesting that the timeline show at least the last N changes. It's not exactly the same request, but closely related, and the two requests should be considered together.
I guess the current default is only problematic when there are no events to be displayed. In this case, we could probably iterate back, period by period, until events are found. Would that be OK?