6.0.0-alpha10
5/14/25

[#8058] The 'day_hour_start' preference is confusing
Summary The 'day_hour_start' preference is confusing
Queue Kronolith
Queue Version Git master
Type Enhancement
State Assigned
Priority 1. Low
Owners wrobel (at) horde (dot) org
Requester wrobel (at) horde (dot) org
Created 03/08/2009 (5911 days ago)
Due
Updated 03/10/2009 (5909 days ago)
Assigned 03/10/2009 (5909 days ago)
Resolved
Milestone
Patch No

History
03/10/2009 08:54:19 AM Jan Schneider Type ⇒ Enhancement
State ⇒ Assigned
Priority ⇒ 1. Low
 
03/09/2009 02:31:26 PM Chuck Hagenbuch Assigned to Gunnar Wrobel
 
03/09/2009 10:02:28 AM Gunnar Wrobel Comment #3
State ⇒ Assigned
Reply to this comment
These are wishes from the Kolab Kosortium/Kolab customers. So far the 
wish has not been contracted but I'd like to track it here to get 
early feedback from your side too. Please assign the issue to me if 
you like (I'm currently not in the Kronolith queue).
03/09/2009 12:37:24 AM Chuck Hagenbuch Comment #2
State ⇒ Feedback
Reply to this comment
I guess extending it to the fb view makes the most sense to me - 
patch? Other opinions?
03/08/2009 09:24:36 PM Gunnar Wrobel Comment #1
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ The 'day_hour_start' preference is confusing
Queue ⇒ Kronolith
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
Reply to this comment
The 'day_horde_start' preference has the description "What time should 
day and week views start, when there are no earlier events?"



The part "..., when there are no earlier events?" holds true for the 
standard day and week views. It does not hold true for the free/busy 
view though. For those views the preference is a fixed setting even if 
earlier events exists.



I think this should be fixed. Either by adding a separate value for 
the free/busy view or by completing the functionality of the 
preference within the f/b view.

Saved Queries