Bug 231143 - Starting date and time not taken into account when creating a to-do over several days
Summary: Starting date and time not taken into account when creating a to-do over seve...
Status: CONFIRMED
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 231147 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-03-17 21:08 UTC by Sabine Faure
Modified: 2010-03-29 00:24 UTC (History)
1 user (show)

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 Sabine Faure 2010-03-17 21:08:50 UTC
Version:            (using Devel)
Compiler:          gcc 4.3.2 
OS:                Linux
Installed from:    Compiled sources

- Launch KOrg
- Click on 'New To-do' button 
- Select a calendar and fill in the title, location, category for the to-do
- Check the 'Start:' check box
- Enter yesterday as a start date and today as a due date
- Click on 'Ok'
- Select the two days in the date navigator view

The to-do is only displayed on the top part of the agenda view for today. Nothing appears on yesterday

Trunk, Svn Rev 1104424
Comment 1 Sabine Faure 2010-03-17 21:12:08 UTC
Similarly:
- Click on 'New To-do' button to create a time bound to do
- Select a calendar and fill in the title, location, category for the to-do
- Check the 'Start:' check box and enter yesterday as a start date
- Check the 'Time associated' check box
- Enter a start time (ex: yesterday at 10:00) and end time (today at 20:00)
- Select the same time zone for the start and end time
- Click on 'Ok'

The same thing happens: the to-do is only displayed for today and instead of being displayed ending at 20:00 it shown in the top part of the agenda view.

Trunk, Svn Rev 1104424
Comment 2 Sergio Martins 2010-03-29 00:20:28 UTC
To-dos are only shown the day they are due. It's also like that in KDE3 and 4.4.

But an option so the user could control this behavior would be handy.
Comment 3 Sergio Martins 2010-03-29 00:24:51 UTC
*** Bug 231147 has been marked as a duplicate of this bug. ***