Bug 246788

Summary:	no due time in "Due Date/Time"
Product:	[Applications] korganizer	Reporter:	Toomas Rosin <toomas>
Component:	todoview	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	smartins, tim.klassen, toomas
Priority:	NOR
Version:	4.4.5
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:

Description Toomas Rosin 2010-08-05 12:27:20 UTC

Version:           4.4.5 (using KDE 4.4.5) 
OS:                Linux

I cannot see the "time" part in the "Due Date/Time" column --- only the date part shows up.  Also, clicking on the column header (to sort the entries by due date/time), the entries are sorted only by date; entries whose date parts are identical are not sorted by due time.


Reproducible: Didn't try

Steps to Reproduce:
View->To-do List; click on the "Due Date/Time" column header


Actual Results:  
Contents of the "Due Date/Time" field should be of the form "yyyy-dd-mm hh:mm"; clicking on the column header should sort the entries by both due date and due time.

Expected Results:  
Contents of the "Due Date/Time" field are of the form "yyyy-dd-mm"; clicking on the column header sorts the entries by due date but not by due time.


OS: Linux (i686) release 2.6.34.1
Compiler: gcc

Comment 1 Tim 2010-09-13 18:43:35 UTC

I also can verify that no time is displayed in the "date due / time" column of the todo display. 

FIX: Either the column header needs to be renamed to just "date due" or the time needs to be displayed beside the date (but only if it is a time associated event).

Comment 2 Denis Kurz 2016-09-24 18:48:45 UTC

This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of korganizer (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.

Comment 3 Denis Kurz 2017-01-07 22:44:37 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.