product_price_history: price inserted in the future displayed as current price
Bug #1295114 reported by
Guewen Baconnier @ Camptocamp
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Financial controlling and costing |
Fix Released
|
High
|
Guewen Baconnier @ Camptocamp | ||
Bug Description
If I insert a price in the future for a product (this is possible using the `to_date` key in the context), then the price is correctly inserted in the product_
Example:
Product A has a price of 100.- today, 2014-03-20.
I insert a price for product A of 200.- for the 2014-06-01.
Now, if I read the price of the product, it displays 200.-, whereas I expect it to be 100.-
This is a corner case but it should be handled correctly.
Related branches
lp:~camptocamp/margin-analysis/7.0-product_price_history-price-in-future-1295114
- Yannick Vaucher @ Camptocamp: Approve (code review, no test)
- Romain Deheele - Camptocamp (community): Approve (code review)
- Alexandre Fayolle - camptocamp: Approve (code review, test)
-
Diff: 73 lines (+38/-5)2 files modifiedproduct_price_history/product_price_history.py (+6/-5)
product_price_history/test/price_historization.yml (+32/-0)
| summary: |
product_price_history: price inserted in the future displayed as current - date + price |
| Changed in margin-analysis: | |
| status: | New → Fix Released |
| assignee: | nobody → Guewen Baconnier @ Camptocamp (gbaconnier-c2c) |
| importance: | Undecided → High |
To post a comment you must log in.
