[6.1/trunk] Invalid commitment date in sale_order_dates module
Bug #1007317 reported by
Yann Papouin
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Odoo Addons (MOVED TO GITHUB) |
Confirmed
|
Low
|
OpenERP R&D Addons Team 2 |
Bug Description
The commitment date which is the "Date on which delivery of products is to be made" is badly computed as it is get from: min(dates_list) it should be max(dates_list) (I agree that it "could" be min if the picking_policy is set to "direct") :
Consider two sale order lines:
Product A: delay to deliver: 8 days
Product B: delay to deliver: 24 days
The commitment date must obviously be the current date + 24 business days
Related branches
lp:~openerp-dev/openobject-addons/trunk-bug-1007317-amp
Rejected
for merging
into
lp:openobject-addons
- OpenERP Core Team: Pending requested
-
Diff: 19 lines (+2/-2)1 file modifiedsale_order_dates/sale_order_dates.py (+2/-2)
summary: |
- [6..1] Invalid commitment date in sale_order_dates module + [6.1] Invalid commitment date in sale_order_dates module |
summary: |
- [6.1] Invalid commitment date in sale_order_dates module + [6.1/trunk] Invalid commitment date in sale_order_dates module |
Changed in openobject-addons: | |
assignee: | nobody → OpenERP R&D Addons Team 2 (openerp-dev-addons2) |
importance: | Undecided → Low |
status: | New → Confirmed |
Changed in openobject-addons: | |
status: | Invalid → New |
To post a comment you must log in.
Hello Yann.
As per the tool-tip it should be maximum date.
Thanks for the pointing out this.
This issue has been committed on lp:~openerp-dev/openobject-addons/trunk-bug-1007317-amp branch with revno 6858 and rev id <email address hidden>.
It will be merge with trunk soon.
Thanks!