Re: Task (WorkEffort) Statuses, any further comments?

2007-12-19 Thread Hans Bakker
Can I ask the community to check the last project Task status proposal? If there are no further comments i will implement the proposal below in a couple of days in the special component 'project manager' The final proposal about the project task status was: The status on a task is largely system

Re: Task (WorkEffort) Statuses, another view

2007-12-15 Thread Jacques Le Roux
I like it, though maybe I would prefer labelling onHold to reviewing. No end task status (resolved, closed)? Is it managed at the project or phase level ? Jacques De : "Hans Bakker" <[EMAIL PROTECTED]> > I thought more about it and like to present a different approach for the > status on a ta

Re: Task (WorkEffort) Statuses, another view

2007-12-15 Thread Hans Bakker
I thought more about it and like to present a different approach for the status on a task. To allow for many approval authorities: Anybody who need to approve the task will be a performer with a appropriate roleTypeId the status on a task is largely system controlled (1-4): 1: unassigned -> th

Re: Task (WorkEffort) Statuses

2007-12-14 Thread Jim Barrows
t; > > > - Accepted (by performer) > > > > - Completed (by performer) > > > > > > To note that the work is currently done, not in a wating state. > > > > > > Jacques > > > > > > - Message d'origine - > > >

Re: Task (WorkEffort) Statuses

2007-12-14 Thread Jacques Le Roux
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 -

Re: Task (WorkEffort) Statuses

2007-12-13 Thread Hans Bakker
state. > > > > Jacques > > > > - Message d'origine - > > De : "David E Jones" <[EMAIL PROTECTED]> > > À : > > Envoyé : mercredi 12 décembre 2007 11:50 > > Objet : Task (WorkEffort) Statuses > > > > > > >

Re: Task (WorkEffort) Statuses

2007-12-13 Thread Hans Bakker
Hi David, I waited a little on my comment because they were already known in the related Jira Issue. I see however some good points in the others so i changed my point of view. first comments on your proposal: isn't 2 statuses for a performer enough? 1. Received/Completed? if a task is received,

Re: Task (WorkEffort) Statuses

2007-12-13 Thread Hans Bakker
d (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]> > À : > Envoyé : mercredi 12 décembre 2

Re: Task (WorkEffort) Statuses

2007-12-13 Thread David E Jones
yé : 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 p

Re: Task (WorkEffort) Statuses

2007-12-13 Thread Jim Barrows
in a wating state. > > Jacques > > - Message d'origine - > De : "David E Jones" <[EMAIL PROTECTED]> > À : > Envoyé : mercredi 12 décembre 2007 11:50 > Objet : Task (WorkEffort) Statuses > > > > > > Hans has started an effort to expa

Re: Task (WorkEffort) Statuses

2007-12-13 Thread Jacques Le Roux
; À : 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

Task (WorkEffort) Statuses

2007-12-12 Thread David E Jones
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