Hi Jacques, Thanks for your interest in this. If a task is completed or not, is documented in the actual enddate.
If the performer reports his time (assumed is dayly) it is known the task is in progress. Further, from my own experience, it is already difficult enough to get people to report their time. With this extra status there will be more burdon on them.... are you still sure we need an extra task status here? Regards, Hans On Thu, 2007-12-13 at 15:12 +0100, Jacques Le Roux wrote: > Maybe a new task status > - In Progress (by performer) > between > > - Accepted (by performer) > > - Completed (by performer) > > To note that the work is currently done, not in a wating state. > > Jacques > > ----- Message d'origine ----- > De : "David E Jones" <[EMAIL PROTECTED]> > À : <[email protected]> > Envoyé : mercredi 12 décembre 2007 11:50 > Objet : Task (WorkEffort) Statuses > > > > > > Hans has started an effort to expand/refine task statuses in this issue: > > > > https://issues.apache.org/jira/browse/OFBIZ-1509 > > > > I think this is complex enough that a mailing list discussion might be > > helpful. > > > > To define the point of this, as I see it, we're trying to create the > > most expansive set of statuses we can, in other all statuses that > > anyone might need or want for a task. The status transitions can then > > take into account that certain statuses don't have to be used, and > > those can of course be added or removed during customization, or other > > things like SECA services can check constraints of course. > > > > Here's a pass at this (based on the current set of statuses, and some > > ideas from Hans in the aforementioned issue): > > > > Roles: > > - client > > - analyst (task creator/writer) > > - task performer > > - peer of performer > > > > Statuses: > > - Needs Action (initial status, from task creator/writer (analyst)) > > - Approved (by client) > > - Sent (to task performer) > > - Accepted (by performer) > > - Completed (by performer) > > - Tested (scope of task, by performer or peer of performer) > > - Reviewed (in perspective of larger scope that task fits into, by > > task creator/writer (analyst)) > > - Changes Needed (failed to go to Tested or Reviewed) > > - Accepted (by client) > > > > - Declined (by performer) > > - Delegated (by performer) > > - On Hold (by client) > > - Cancelled (by client) > > > > That's a fairly quick first pass... anyone have any thoughts on other > > roles or statuses (ie steps in the process)? > > > > -David > > > > > > -- http://Antwebsystems.com : OFBiz Quality support for competitive rates.
