(*** This bug was imported into bugs.kde.org ***) Package: korganizer Version: 3.0.2 (using KDE 3.0.2 ) Severity: wishlist Installed from: (3.0) Compiler: gcc version 2.95.4 20011002 (Debian prerelease) OS: Linux (i686) release 2.4.18-bf2.4 OS/Compiler notes: Here's an idea. We all know about recurring todos but consider this twist on them (an option) For a todo that happens say once a month (or whatever period of time.) It doesn't need to happen exactly once a month but when it does get completed (wether late or early) it schedules itself for one month from the completion date. Example (contrived) Haircut. I get one about once a month but I can let it go two or three weeks if nothing special is coming up (or I don't have it in KOrganizer and forget). So I get July's haircut three weeks late and instead of schedule the next recurrance in the beginning of August it schedules it for one month later. Just a thought. (Submitted via bugs.kde.org) (Called from KBugReport dialog)
*** Bug 84466 has been marked as a duplicate of this bug. ***
This is very important, I use it for a lot of items on my Palm Pilot and would like to be able to use them the same way on my PC. No free software calendar/todo program I know of can do this!
I'll add another situation in which something like this would be useful: Legal filings. Upon making one filing, a whole list of other filings are automatically scheduled to come due. The entries to be added could be handled, for instance, on a per-category basis. Different types of filings have different schedules of events that they "trigger". Although this example is a bit more complex than a haircut, which just needs to recur, it's something to think about when implementing this feature.
Reassigning all KOrganizer bug reports and wishes to the newly created korganizer-devel mailing list.
*** Bug 121853 has been marked as a duplicate of this bug. ***
If you want this done, please describe what concrete modifications and strings should be done in the UI. Don't forget that the old/current behavior should still be an option, it won't be removed because there are lots of use cases for it, for example, paying bills.
This is handled by todo exceptions. Create a todo with summary "hair cut" recurring every 1 month, starting in June. When you get your July hair cut, drag the July occurrence to the date when the cut happened, and select "Also Future Items" in the dialog. The August occurrence will also move, to 1 month after the July cut.
(In reply to gjditchfield from comment #7) > This is handled by todo exceptions. Create a todo with summary "hair cut" > recurring every 1 month, starting in June. When you get your July hair cut, > drag the July occurrence to the date when the cut happened, and select "Also > Future Items" in the dialog. The August occurrence will also move, to 1 > month after the July cut. In my opinion this is not an optimal way of handling these cases. One would have to adjust the task each time it is completed. Lately I've been using this app for Android: https://f-droid.org/packages/org.tasks/ . It handles the use case we're talking about in what I would consider to be a good way.