- Aug 27, 2015
-
-
Nicolas Martinelli authored
Major changes: - No use of UoS anymore - Partial migration to new api Reason: complete rewrite of the Sale module. Responsible: fp, dbo, nim
-
Nicolas Martinelli authored
Major changes: - No use of UoS anymore - Remove invoicing process Reason: complete rewrite of the Sale module. Responsible: fp, dbo, nim
-
Nicolas Martinelli authored
New module to be able to link timesheet on a sale order. Reason: complete rewrite of the Sale module. Responsible: fp, dbo, nim
-
Nicolas Martinelli authored
Major changes: - No invoicing anymore - Migration to new api Reason: complete rewrite of the Sale module. Responsible: fp, dbo, nim
-
Nicolas Martinelli authored
Major changes: - Link with account analytic lines Reason: complete rewrite of the Sale module. Responsible: fp, dbo, nim
-
Nicolas Martinelli authored
Major changes: - Recalculate date planned Reason: complete rewrite of the Sale module. Responsible: fp, dbo, nim
-
Nicolas Martinelli authored
Major changes: - No use of UoS anymore - Manage delivery of kits Reason: complete rewrite of the Sale module. Responsible: fp, dbo, nimproduct_id_change_margin
-
Nicolas Martinelli authored
Major changes: - No use of UoS anymore - Rewrite product_id_change_margin Reason: complete rewrite of the Sale module. Responsible: fp, dbo, nim
-
Nicolas Martinelli authored
Major changes: - No use of UoS anymore Reason: complete rewrite of the Sale module. Responsible: fp, dbo, nim
-
Nicolas Martinelli authored
Reason: complete rewrite of the Sale module. Invoicing is now managed through Sale. Responsible: fp, dbo, nim
-
Nicolas Martinelli authored
Links expenses and sale modules. Reason: complete rewrite of the Sale module. Responsible: fp, dbo, nim
-
Nicolas Martinelli authored
-
Nicolas Martinelli authored
Reason: complete rewrite of the Sale module. Invoicing is now managed through Sale. Responsible: fp, dbo, nim
-
Nicolas Martinelli authored
Invoicing is now completely handled from the SO. cf. documentation Reason: complete rewrite of the Sale module. Responsible: fp, dbo, nim
-
Nicolas Martinelli authored
Major changes: - No use of UoS anymore Reason: complete rewrite of the Sale module. Responsible: fp, dbo, nim
-
Nicolas Martinelli authored
Reason: complete rewrite of the Sale module. Invoicing is now managed through Sale. Responsible: fp, dbo, nim
-
Nicolas Martinelli authored
Major changes: - No use of UoS anymore Reason: complete rewrite of the Sale module. Responsible: fp, dbo, nim
-
Nicolas Martinelli authored
Major changes: - New start and expiration dates - Remove field Contract Status - Simplified because use of sale_timesheet Reason: complete rewrite of the Sale module. Responsible: fp, dbo, nim
-
Nicolas Martinelli authored
New module to centralize UoS management. Reason: complete rewrite of the Sale module. Responsible: fp, dbo, nim
-
Nicolas Martinelli authored
Major changes: - No use of UoS anymore - Partial migration to new api Reason: complete rewrite of the Sale module. Responsible: fp, dbo, nim
-
Nicolas Martinelli authored
Major changes: - No use of UoS anymore Reason: complete rewrite of the Sale module. Responsible: fp, dbo, nim
-
Nicolas Martinelli authored
Major changes: - No use of UoS anymore Reason: complete rewrite of the Sale module. Responsible: fp, dbo, nim
-
Nicolas Martinelli authored
Major changes: - No use of UoS anymore Reason: complete rewrite of the Sale module. Responsible: fp, dbo, nim
-
Nicolas Martinelli authored
Major changes: - No use of UoS anymore Reason: complete rewrite of the Sale module. Responsible: fp, dbo, nim
-
Nicolas Martinelli authored
Major changes: - No use of UoS anymore - No use of Journal Name Reason: complete rewrite of the Sale module. Responsible: fp, dbo, nim
-
Nicolas Martinelli authored
Major changes: - No use of UoS anymore Reason: complete rewrite of the Sale module. Responsible: fp, dbo, nim
-
Nicolas Martinelli authored
Reason: complete rewrite of the Sale module. Invoicing is now managed through Sale. Responsible: fp, dbo, nim
-
Nicolas Martinelli authored
Major changes: - No use of UoS anymore - No journal since invoicing is managed in Sale - No invoicing from timesheet Reason: complete rewrite of the Sale module. Responsible: fp, dbo, nim
-
Nicolas Martinelli authored
Reason: complete rewrite of the Sale module. Responsible: fp, dbo, nim
-
Nicolas Martinelli authored
Major changes: - No use of UoS anymore - No invoice policy anymore Reason: complete rewrite of the Sale module. Responsible: fp, dbo, nim
-
Nicolas Martinelli authored
Reason: complete rewrite of the Sale module. Analytic has been simplified. Responsible: fp, dbo, nim
-
Nicolas Martinelli authored
Reason: complete rewrite of the Sale module. Invoicing is now managed completely from the Sale module. Responsible: fp, dbo, nim
-
Nicolas Martinelli authored
Major changes: - Remove reports - Simplify models Reason: complete rewrite of the Sale module. Responsible: fp, dbo, nim
-
Nicolas Martinelli authored
Major changes: - No use of UoS anymore - No analytic account journal on account journal Reason: complete rewrite of the Sale module. Responsible: fp, dbo, nim
-
Nicolas Martinelli authored
Reason: complete rewrite of the Sale module. Responsible: fp, dbo, nim
-
Nicolas Martinelli authored
Major changes: - No use of UoS anymore - No analytic journal (journal_id) on account move lines Reason: complete rewrite of the Sale module. Responsible: fp, dbo, nim
-
Nicolas Martinelli authored
Reason: complete rewrite of the Sale module. Invoicing is now managed completely from the Sale module.
-
Nicolas Martinelli authored
Reason: complete rewrite of the Sale module
-
Joren Van Onder authored
Fixes a bug introduced in 5a8a0d25. Before this, creating an order with two of the same products would result in a total price to pay which would only include the tax of one product. This would cause point of sale orders in the backend which weren't fully paid.
-
Thibault Delavallée authored
- hr, project, sales_team: no subscribe on create For header records like sales steam, project, jobs and department, do not subscribe the creator. Indeed those objects allow to automatically follow child records (opportunities, tasks, issues, applicants). However those records are often created by IT / technical / administrators that should not be followers of all child records. Therefore the no subscribe key is added in context. - crm: new lead subtype The 'new' stage is based on the sequence only, not the probability. Indeed a new lead does not have a probability of 0; otherwise it is already lost.
-