Bug 132728

Summary: Marking a mail as "pending task" should generate a task in Kontact
Product: [Applications] kontact Reporter: Iñaki Baz Castillo <ibc>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: wishlist    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Iñaki Baz Castillo 2006-08-21 00:30:33 UTC 
Version:           desconocido (using KDE 3.5.4, Kubuntu Package 4:3.5.4-0ubuntu2~dapper1 )
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.15-26-386

Kmail offers the possibility of marking a mail as "pending task". It's great but it could be more useful if that task appears integrated in the tasks of Kontact.

It could appear as a new task with "mail" category, the sumary could be the subject of the mail and the description the mail body. And it could appear a "mail" icon the user to understand quickly that it's a mail.

Of course both should be syncronized, so if the users deletes or marks the task as completed in Kontact the mail should be automatically marked as no task. And if the user marks the mail as no task in Kontact it should appear as completed.

It could improve the integration of Kontact apps.

Regards.
Comment 1 Stefan Haun 2006-08-24 21:33:22 UTC 
The biggest problem I see is the tight coupling between kmail and korganizer this feature would lead to. An appointment cannot be created without having korganizer installed - but an advantage of the kontact suite are the independent components.


What about the following:
In KMail, there is an option "Create Task" in every e-mail which would create a task in KOrganizer via DCOP, or DBus for KDE4. With a kontact kio slave, it would even be possible to attach the mail to the task.

With this solution, there is no dependency between the two tools, apart from the DCOP call. The mail may be moved or deleted without affecting the task.


Synchonization between the task and the e-mail would require some linkage. This cold be done via the attachment in the task (kio slave...) and a field in the mail header (X-KTask-ID?). Something alike...


What ever the solution looks like, it should not make both the tools dependend from each other.
Comment 2 Iñaki Baz Castillo 2006-08-24 21:53:32 UTC 
Great proposal!
Comment 3 Bram Schoenmakers 2006-10-29 14:06:44 UTC 

*** This bug has been marked as a duplicate of 103753 ***