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
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
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
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
Fixes a bug introduced in 5a8a0d252c.
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.
- 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.
- mail_message: fixed internal subtypes
Indeed has_group works only for uid and does not care for any given recordset.
Probably we need a is_in_group method on res.users. Someone smart could code it.
- mail_message: update message before notify
This way in the various notify methods, the message is correclty updated with
needaction and recipients. Also cleaned some comments.
- mail_message: avoid email loops
Do not notify people having the same email as the message / email to propagate.
- mail_message: fix access right issues
When computing recipients and partners to email, use a sudo for some internal
computation to avoid access rights issues. Indeed public user may go through
this method (forum for example).
Employees (base.group_user) can read tasks. However they miss the right to read
task stages (project.task.type). This causes issues when reading the form view
of a task. This commit fixes this issue.
In sales_team, we had 2 fields for invoicing : invoiced_target and invoiced_forecast.
As forecast is useless because someone has to set it manually, we did something different.
The field invoiced_forecast is now invoiced and is computed according to the invoices
associated to the sales team. We can now only set the target.
When posting a comment, the user can rate the product using rating star widget. The rating card is display on the product page with average and repartition.
Add a related field 'website_published' on rating in website_sale for performance issue.
Part of this commit could be moved in 'website_rating', if the feature is required in other modules. Since it is only used in ecommerce, the code belong to website_sale.
Nicolas Martinelli