Summary: | journal entries form To-Do List | ||
---|---|---|---|
Product: | [Applications] korganizer | Reporter: | Wilm Kob <wilmkob> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | CONFIRMED --- | ||
Severity: | wishlist | CC: | mikmach |
Priority: | NOR | ||
Version First Reported In: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Wilm Kob
2005-05-10 14:59:00 UTC
When you mark a to-do as finished, korganizer already has the option to log this to a journal. Does this suffice? Cheers, Reinhold Looked into it and current implementation is short on details: - no localization - no description - no attendees - no info on time of complete - no info about priority - no info about attachments - no date of creation Such entry should be complete record of original to-do. And each to-do should be in *separate* journal entry. BTW. I wonder if journal entries can have (iCal limitations) rich text elements like bold text, emphasised, lists, links. I wonder, why the journal is limited to text entries. What about storing entries as what they originaly were? Tasks as tasks, appointments as appointments and additionally the user may add text entries. So tasks and appointments could be added without loosing any information and even be recovered from the journal. A plus would be to journal e-mail activity, which enables to completly follow a process via the journal. If logging of karm activities would be added, I were able to reconstruct the work done over a day via my journal which would boost the tool. :) Reassigning all KOrganizer bug reports and wishes to the newly created korganizer-devel mailing list. |