c2c-oerpscenario team mailing list archive

["Olivier \(Open ERP\)" <660554@xxxxxxxxxxxxxxxxxx>]

** Description changed:

  This is probably a general issue but I'll take 'tasks' as an example.
  
  For a task to be displayed in a gantt chart, it's starting date should
  be set. But sub tasks should be displayed as well, otherwise the gantt
  chart is not useful. But you can't compute the starting date of sub
  tasks manually.
  
  Normally, the starting date of a sub task should be equal to (the
  starting date  + the delay) of it's parent
  
  Some solutions:
  
   * a wizard computing the starting date of sub tasks based on starting date of the root task and the delays of it's sub tasks (not optimal because that wizard should be run every time a delay or a starting date is changed)
   * not setting a starting date for sub tasks but the gantt chart engine should compute all task delays based on the root task
  
+ Perhaps we could borrow the code used in the mrp module for the work
+ orders object (end date computation)
+ 
  version: trunk
  client: web

-- 
Tasks in Gantt chart: delay should take parent tasks into account
https://bugs.launchpad.net/bugs/660554
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to OpenERP OpenObject.

Status in OpenObject Addons Modules: New

Bug description:
This is probably a general issue but I'll take 'tasks' as an example.

For a task to be displayed in a gantt chart, it's starting date should be set. But sub tasks should be displayed as well, otherwise the gantt chart is not useful. But you can't compute the starting date of sub tasks manually.

Normally, the starting date of a sub task should be equal to (the starting date  + the delay) of it's parent

Some solutions:

 * a wizard computing the starting date of sub tasks based on starting date of the root task and the delays of it's sub tasks (not optimal because that wizard should be run every time a delay or a starting date is changed)
 * not setting a starting date for sub tasks but the gantt chart engine should compute all task delays based on the root task

Perhaps we could borrow the code used in the mrp module for the work orders object (end date computation)

version: trunk
client: web