Bug 195707 - Effect of setting % completed on recurring to-dos is unintuitive.
Summary: Effect of setting % completed on recurring to-dos is unintuitive.
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: incidence editors (show other bugs)
Version: 4.2.2
Platform: Ubuntu Unspecified
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-08 21:03 UTC by Ian Turner
Modified: 2017-01-07 22:28 UTC (History)
2 users (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 Ian Turner 2009-06-08 21:03:41 UTC
Version:            (using KDE 4.2.2)
Installed from:    Ubuntu Packages

STEPS TO REPRODUCE:

. Create a new recurring to-do.
. Open the to-do's edit dialog and select 100% completed.
. The dialog allows the user to set a "completed time".
. Press OK

ACTUAL BEHAVIOUR:

The to-do's completed status is reset to 0%, and the due date is updated to the next occurrence.

EXPECTED BEHAVIOR:

The dialog should provide some feedback that the actual behavior will take place.

My suggestion would be to replace the "completed on" text and fields with something like:

+------+
|100% ▼| completed: this task will recur on <date/time>
+------+
Comment 1 Janet 2009-12-18 14:37:59 UTC
But the completion percentage should go back to 0% after that! Because for the next due date it actually *is* 0% completed!
Comment 2 Ian Turner 2009-12-18 22:56:06 UTC
Janet, yes, I was expecting the % completed to return to zero after the user clicks OK. Also the due date should change to the next due date at that time. The question here is basically what feedback the user gets that this is happening.
Comment 3 Denis Kurz 2016-09-24 18:48:02 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 4 Denis Kurz 2017-01-07 22:28:15 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.