+1
David E Jones sent the following on 7/17/2008 6:23 AM:
>
> That doesn't mention anything about having statuses just for the project
> manager component, just some talk about a series of statuses.
>
> Why is there a need for different statuses than the main ones?
>
> It would be a lot better to have a single set for any task management
> application based on OFBiz, especially one that is part of the
> project... hopefully we can avoid fragmentation at least at that level!
>
> Ideally any project/task/etc management application based on OFBiz could
> run with data from another such application.
>
> Just so you know, we're working on a fairly custom small set of screens
> (like 5-6 screens) for our use at Hotwax, and we're ending up avoiding
> much of what is in the project manager specialpurpose app in order to
> use the more "standard" patterns in the workeffort component. There have
> been various questions and discussions around this on the mailing lists,
> and a few commits from me recently to flesh out the data model to add
> little things that we ran into that didn't exist.
>
> -David
>
>
> On Jul 16, 2008, at 2:03 PM, Hans Bakker wrote:
>
>>
>> David, please look at: https://issues.apache.org/jira/browse/OFBIZ-1509
>>
>> On Wed, 2008-07-16 at 13:20 -0600, David E Jones wrote:
>>>
>>> On Jul 16, 2008, at 8:02 AM, Hans Bakker wrote:
>>>
>>>>
>>>> Hi Adrian,
>>>>
>>>> the difference is as I already mentioned in the component selection
>>>>
>>>> the projectmanagement has 2 selections which are project management
>>>> specific:
>>>> <field-map field-name="workEffortTypeId" value="TASK"/>
>>>> <field-map field-name="currentStatusId" value="PTS_CREATED"/>
>>>>
>>>> these status and type were specifically created for the projectmanager
>>>> and are not used for selection in the workeffort manager.
>>>
>>> I would be quite interested in hearing why this was done...
>>>
>>> -David
>>>
>>>
>>
>
>
>
>
