Version: (using KDE 3.5.8) Installed from: I Don't Know OS: Linux Hello, I wrote that idea to Kdepim-users list half year ago. It was missed there. Now will try to exlain it here. :) I'm Using Kontact more than 2 years and really like this application, it's best PIM solution for linux, and one of the best solutions for all OS. But still some things can be improved. Some time ago I invested time for reading books about time management. Let me share experience. Lets talk about task priorities. Almost all time management experts propose to use so called ABC system. You can find some info about it in wikipedia: http://en.wikipedia.org/wiki/Time_management#ABC_analysis But, let me describe more precise: There are 4 levels of priorities: A, B, C, D: A - Critical and time sensitive tasks. Those must be done immediately. If it done it may give super results, if not - cause serious consequences. B- Important but less time sensitive tasks. They can be postponed but not for long. After some time they can rise to A priority. C- not time sensitive tasks. They can be delayed without serious consequences. If tied to distant competition date - will eventually rise to B or even A priority when deadline approaches. D- optional - nice, but not important and not time sensitive tasks. It never rise to B or C. Theoretically you don't need to do it. For example to go to movie, or read a book, to buy flower for wife etc. How it looks now in Korganizer? From usability point of view 10 levels of priority are to many. What difference between 3 or 4, 7 or 8? Only big corporations need to use so many levels in groupware suites. Most people use only 3 priority levels (1-5-10). So, we can add some 'science' of time management to Korganizer and make life easier for many people (including me). How it can be integrated in Korganizer? Minimal program (step 1) - just leave 4 of 10 now existing priorities. Merge 1 and 2, 3 and 4, etc. Make a tips about ABC system (I can write it, if anyone will fix my English). Full integration (step 2) to KOrganizer: 1. When A priority is set - tasks marked red, reminder is enabled by default. 2. When B priority is set - reminder is enabled by default, when task is overdue, priority automatically changes to A, user is informed about that by reminder daemon. 3. When C priority is set - reminder is disabled by default, when task is set for more then one month, last 10% of time is left it changes to B, if task is overdue priority changes to A. User is informed about all changes by reminder daemon. 4. When D priority is set - reminder is disabled by default, if task is unfinished after end time, it is deleted. Changes in summary page- Tasks are grouped by priority A tasks on top, D on bottom. Hope you like idea Regards, Dumas
I like this idea to give different behavior on the priority levels! It should be implemented on the new task list. Moreover I'll prefer to have 5 priority levels, not 4. But I've a question: if you need to sync your tasks with another app which use ten priority levels what should happen?
I do not see big difference between 4 or 5 priority levels. 4 levels are most common in task management, so I was thinking just to use ABC system without reimplementing the wheel. h Actually I do not know any other PIM software which uses 10 priority levels. Ms Outlook uses 3 levels. No Idea about evolution or Sunbird... Answer to your question: we can use average level in middle and min/max levels on high-low priority tasks, e. g. 1=1, 2=4, 3=7, 4=10.
Yes, it could be. :-)
I'm ok with this idea. Can you write code? We are very short on manpower to implement this.