[Korganizer-devel] [Bug 278440] New: feature request: enable time management with tasks

[kdebug at merctech.com]

https://bugs.kde.org/show_bug.cgi?id=278440

           Summary: feature request: enable time management with tasks
           Product: korganizer
           Version: 4.4.11
          Platform: Fedora RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: general
        AssignedTo: korganizer-devel at kde.org
        ReportedBy: kdebug at merctech.com


Version:           4.4.11 (using KDE 4.6.5) 
OS:                Linux

Tom Limoncelli describes a "Cycle System"  for ordering tasks in great detail
in his book, Time Management for System Administrators.

It would be a tremendous enhancement to implement such a system, and would
have wide use.

The basic concept is that tasks are assigned a duration and category,
and optionally a level of importance and a due date.

Based on the duration of each task, and user-preferences for time
categories & work hours, tasks are arranged to fill each time period.

Each day, Kontact (korganizer) would rearrange uncompleted tasks as needed,
using a knapsack packing algorithm.

Any uncompleted events that are scheduled in the past will automatically
rescheduled to the current/future date (optionally increasing the priority
so that deferred tasks gain importance over time).

For each day, events or tasks with pre-defined times (ie., fixed time periods,
not just a duration) take precedence, so that automatically scheduled tasks
are packed around those blocks of time.

The user would define time periods, such as:
    Work: Mon-Friday 9-5pm (lunch 12-1pm)
        Evening: Sunday-Saturday 8pm-11pm
        Weekend: Saturday-Monday 10am-10pm

When entering a new task, the user would specify the category based on time
(ie., "work week", "evening", "weekend").

The user would specify an "expected duration" for events (not a fixed
start/ end time).

        Optional: specify an priority for events

        Optional: specify a start deadline for events (ie.,
        event must not start before a particular date/time)

        Optional: specify a finish deadline for events (ie.,
        event must be completed by a particular date/time)


------------------- Example -------------------------------------

For example, the on Sunday user might enter the following tasks:

    Task:    configure web server
    Duration: 2hr
    Category: work

    Task:    create account for John Doe
    Duration: 15min
    Category: work

    Task:    install IMAP
    Duration: 1:30hr
    Category: work

    Task:    restore data for Jane Smith
    Duration: 4hr
    Category: work
    Priority: 1

    Task:    configure new SAN
    Duration: 4hr
    Category: work

    Task:    research converting all PHP scripts to Ruby
    Duration: 3hr
    Category: work

    Task:    order new network cables
    Duration: 15min
    Category: work

Those tasks won't fit into the 7hrs available per day in the category
"work", and 2 tasks can only fit into the block of time after lunch,
so the schedule on Monday might look like:

    Monday 9:00 - 9:15    create account for John Doe
    Monday 9:15 - 10:45    install IMAP
    Monday 10:45 - 11:00    order new network cables
    Monday 13:00 - 17:00    restore data for Jane Smith

    Tuesday: 9:00 - 11:00    configure web server
    Tuesday: 13:00 - 16:00    research converting all PHP scripts to Ruby

    Wednesday: 13:00 - 17:00    configure new SAN

If the task "install IMAP" didn't get done on Monday, it would automatically
be moved to Tuesday, with one of Tuesday's tasks moving to Wednesday.

Reproducible: Didn't try



Expected Results:  
NA

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.