This website requires JavaScript.
Explore
Help
Sign In
Elabore
/
odoo-usability
Watch
9
Star
0
Fork
0
You've already forked odoo-usability
Code
Issues
Pull Requests
Actions
Packages
Projects
Releases
Wiki
Activity
Files
2c1b8fe657f4b9ddf3355e1b0855c4e7fccb10c1
odoo-usability
/
sale_usability
History
Alexis de Lattre
054bee90c0
Add module sale_force_invoice_status
2018-02-02 18:27:22 +01:00
..
i18n
Remove modules that will be merged in ***_usability modules or that are not useful in v10
2016-10-11 15:27:34 +02:00
__init__.py
Add traking on warn fields
2017-04-05 19:22:01 +02:00
__manifest__.py
Add module sale_force_invoice_status
2018-02-02 18:27:22 +01:00
partner.py
Add traking on warn fields
2017-04-05 19:22:01 +02:00
product_view.xml
Add menu entry on product.pricelist.item
2017-01-10 17:51:15 +01:00
product.py
Add traking on warn fields
2017-04-05 19:22:01 +02:00
sale_view.xml
Add sum=1 on several qty fields
2017-11-30 12:06:02 +01:00
sale.py
sale_usability purchase_usability: reload form view upon sale order and purchase order confirmation to display the 3 qty columns
2017-12-07 14:52:10 +01:00