Bug 237016 - I cannot see the start date of a TO-DO in list view
Summary: I cannot see the start date of a TO-DO in list view
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-09 21:20 UTC by Parameshwara Bhat
Modified: 2017-01-07 22:08 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Parameshwara Bhat 2010-05-09 21:20:36 UTC
Version:           4.4.3 (using 4.4.3 (KDE 4.4.3), KDE:KDE4:Factory:Desktop / openSUSE_11.2)
Compiler:          gcc
OS:                Linux (i686) release 2.6.31.12-0.2-desktop

I started using Korganiser after a long-time.I added TO-DOs,then set their due date and start date.The TO-DO view itself does let me add start date column.I expected in the DAY view I would see the tasks listed for the day.NO.They are not listed there.
In business tasks take time for completion.They do not happen in one day.And it is not that I start every task at a fixed time,as an event.I schedule many tasks for a day,they have dependencies on other tasks and see how the day goes.So,when a task is given a start date,they should be listed for the day,even if not set a specific start time.
The TO-DO lists should have configurable columns.IN the least,start date column should be there.
I see two inadequacies,if they can be called bugs here;

1. Tasks not appearing on the START day in the day view
2. No start date in the TO-DO list
Comment 1 Denis Kurz 2016-09-24 18:51:24 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 2 Denis Kurz 2017-01-07 22:08:08 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.