Odoo Changelog — 2016-06-29

Wednesday, June 29, 2016

1 change · master

New Features(1)

New functionality added to Odoo

Forecasting grid view

Enterprisemastergridproject_forecastproject_forecast_gridproject_forecast_saleHigh impact

Adds a grid-based view for entering and reviewing project forecasts, including monthly planning by task, totals, and flexible reporting spans. This helps teams plan staffing and project workload more clearly, especially for projects created from sales orders.

Original PR description

!! WARNING!! Due to needs of client project, this branch has been rebased on saas-11 and moved to enterprise/saas-11-forecast-grid-xmo, to eventually merge in master/saas-12 ### grid views for…

!! WARNING!! Due to needs of client project, this branch has been rebased on saas-11 and moved to enterprise/saas-11-forecast-grid-xmo, to eventually merge in master/saas-12
### grid views for project forecasts
- forecast input is monthly-only
  - sectioned by task
  - the project must have a start and end date (wizard added to fill them in case they're missing), this will define the width of the grid (no pagination)
- forecast "reports" with various groupings and spans
- forecasts automatically enabled on projects created from sale orders (via link module, projects are not forecastable by default)
### changes/fixes to the grid view
- reimplemented on [a fairly simple vdom](https://github.com/paldepind/snabbdom) (450LOC)
  - greatly simplifies updating in-place
  - especially with the addition of sections
- grid sections with intermediate (by-section) and grand totals
- improved adjustment (update of a cell's value)
  - configurable as an action or a method call (same as a button)
  - can return further action to execute (and wait on)
- have adjustment method potentially return an action to execute (and wait on)
- added stepping and pagination hook methods for date columns, and support for more steps and spans
### changes to project.forecast
- resource_hours becomes the reference field
- time becomes a float (formerly an int) computed only if there's a resource calendar set up for the forecast user
- forecasts start and end on a date (formerly a datetime)

#forecasting#project planning#grid view#resource planning

!! WARNING!! Due to needs of client project, this branch has been rebased on saas-11 and moved to enterprise/saas-11-forecast-grid-xmo, to eventually merge in master/saas-12 ### grid views for project forecasts - forecast input is monthly-only - sectioned by task - the project must have a start and end date (wizard added to fill them in case they're missing), this will define the width of the grid (no pagination) - forecast "reports" with various groupings and spans - forecasts automatically enabled on projects created from sale orders (via link module, projects are not forecastable by default) ### changes/fixes to the grid view - reimplemented on [a fairly simple vdom](https://github.com/paldepind/snabbdom) (450LOC) - greatly simplifies updating in-place - especially with the addition of sections - grid sections with intermediate (by-section) and grand totals - improved adjustment (update of a cell's value) - configurable as an action or a method call (same as a button) - can return further action to execute (and wait on) - have adjustment method potentially return an action to execute (and wait on) - added stepping and pagination hook methods for date columns, and support for more steps and spans ### changes to project.forecast - resource_hours becomes the reference field - time becomes a float (formerly an int) computed only if there's a resource calendar set up for the forecast user - forecasts start and end on a date (formerly a datetime)