[Planner] Re: Planner Digest, Vol 8, Issue 5

[Ron Tidd <ron tidd net>]

Looking much better!

I have a couple questions/requests though.
I set up a postgres DB to use the save to DB.
Save works the first time.
Save adds another instance (id) for each subsequent save.
Open from database kills planner.

I assume that will be fixed shortly however.
I am running planner 0.11

Here however is my wish list...
I would love to use planner at work.
I need the ability for multiple PM's to update to a central DB.
I need (and am willing to code) a web interface for reporting purposes,
and for the programmers/etc to update the status of a task (as in
additional notes and % complete.)

It would be very cool if the PM had a version ID for each element stored
in planner.  Then when saving the days changes back to the DB a
mechanism would automatically merge the saved changes into the DB, load
the already saved changes for task status and other sections modified by
other PMs, and finally prompt the PM on items that contain updates on
the same element. (A simple dialog for Overwrite DB/ Overwrite local
data / Edit info before overwriting  would work wonders here)

If versioning of elements can be added, planner blows away the
competition.  Imagine having a web I/F for people to check status.  For
those that are assigned tasks to be able to add notes and update status
on a task, and multiple PMs allowed to work on (separate?) parts of a
bigger project...  Then this becomes a killer ap that justifies
purchasing a system that supports planner.