[
https://issues.apache.org/jira/browse/OFBIZ-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12583456#action_12583456 ]
David E. Jones commented on OFBIZ-1725:
---------------------------------------
Why would any data model change be necessary? There are plenty of fields and entities that relate WorkEfforts one to another.
On a side note, to quote from that wiki page: "A WBS is not an exhaustive list of work. It is instead a comprehensive classification of project scope. A WBS is not a project plan or a project schedule and it is not a chronological listing."
This is just an artifact to use in advance of planning a project to make sure you get all of the pieces in place and planned for. Still, either way, the most that could possibly be needed for something like this is a new WorkEffortAssocType, either to associate the WBS (WorkEffort) to a Project (WorkEffort), and/or to associate a parent in a WBS to a child in the WBS (though the parent work effort id could also be used for that).
> Add a WBS (Workbreakdown structure) to every task/phase/project in the system
> -----------------------------------------------------------------------------
>
> Key: OFBIZ-1725
> URL:
https://issues.apache.org/jira/browse/OFBIZ-1725> Project: OFBiz
> Issue Type: New Feature
> Components: specialpurpose/projectmgr
> Affects Versions: SVN trunk
> Reporter: Hans Bakker
> Fix For: SVN trunk
>
>
> In order to able to identify structure in a project the WBS id needs to be added.
> Theoretical background can be found at:
http://en.wikipedia.org/wiki/Work_breakdown_structure> I would suggest a new field in workEffort although there are certainly other ways to do this.
> The population of this field could be automated a lot, although manual adjustment will be required.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Locked
