In a company, there might be several contract types, e.g.:
- 38 Hours/Week, 5 Days/Week
- 45 Hours/Week, 5 Days/Week
- 24 Hours/Week, 2 Days/Week (work on week-end only)
Therefore, it is necessary to be able to define the average number of
hours per day on a resource calendar.
The domain used to search the project issues in the website_project_issue
controller(['/my', '/my/home']) was useless thanks to the ir.rule portal_issue_rule
opw:676447
When a form view had only one field, it was fullwidth.
Now we add a separator automatically. That (seems) have no
effects on model with several field and fix the display when
only one field.
Estimate the workcenter cost based on produced quantity so far.
The workcenter cost is written on analytic accounts at the end of the production
only. A new method _compute_costs_from_production is needed to estimate the
workcenter total cost and then divide by the produced unit.
opw-675994
If the production flow is in two steps:
1. consume raw material
2. produce manufactured product
The total_consume_moves was empty (so computed cost was 0)
Include the moves that were already consumed since the last production.
This will offer a correct estimation of cost of production in real time for
companies producing in several steps.
opw-675994
Follow up of fix 6f8030a
This previous fix removed the reference field when creating an
invoice from a sales order since this field was for Supplier
Invoices (and is not shown for Customer Invoices).
While this males sense, it had the side effect of removing the
default value for the "Register Payment" wizard.
To keep this wizard populated with the most sensible data,
the default is now set to reference or name or number (in that
order).
opw 676261
In Discuss, if a message was selected as message to reply to, it wasn't reset
when switching to another channel. So if the user sent a message in that other
channel, the message was sent as reply to the previously selected message.
This rev. ensures to always unselect messages when switching between channels.
Closes#11879
Before this, if you where on the customer selection screen and scanned a
customer barcode the customer would be shown, but you were not able to
select him.
This correctly sets ClientListScreenWidget.new_client to the scanned
partner which makes the button toggle.
Closes#11874
available in channels and chats, but not livechats as the public user isn't
really "in" the channel (the command would reply that you are alone in the
channel, which isn't necessarily the case)
Use the mention mechanism of the composer to autocomplete on canned responses
(keyword :) with fuzzy search.
Directly perform the string replacement in the composer, instead of
server-side as before.
Add a menu item to access an editable list view to create and edit canned
responses.
Add two canned responses as demo data.
to prevent crashes if the user types, e.g. a \, in the partner's autocompletes
in Discuss ('Add a DM' in sidebar and 'Invite people to channel' dialog).
A 200ms delay is set on lookups for mention suggestions to prevent triggering
RPCs when the user is still typing. However, there shouldn't be a delay when
the suggestions are looked up in the prefetched suggestions.
Also fixes a bug that might occur when the user starts typing a mention which
triggers an RPC, but erase it before the RPC returns.
The BasicComposer widget is now used in chat windows, which enables the mention
feature. This is only for the backend, as for the livechat windows in the
frontend, the composer is still a simple input.
Classname 'o_chat_input' has been renamed into 'o_chat_composer' (the root
classname of the basic composer) for uniformity in the JS and LESS code of
chat windows.
It's needed by the onchange on product_id. Without this the price will
be correctly computed by `onchange_product_id` but upon saving the
record tax_ids will be lost.
Closes#11875Closes#11705Closes#10378
* removed hr.timesheet.report as it's mostly redundant with regular
views on analytic lines
* moved "detailed activities" to reporting, renamed it, added a pivot
view
* redirected timesheet link from HR dashboard to the detailed activities
action
- added department_id to analytic lines as that link is filtered by
department
- fixed bug in kanban view: button context wasn't evaluated in the
correct context
The followers of the departments subscribed to the
`Leaves/Allocations Confirmed` are supposed to
receive a mail notification when an employee
confirms a leave request.
It was no longer the case since the below revision:
2be1dfc1ed
This revision subscribes the followers of the department
following the `confirmed` subtype manually
,on the leave request confirmation, because
`message_auto_subscribe` only works on fields for which
the value is passed to the `create` or `write` methods,
it doesn't work for related/computed fields
This can be removed as soon as `department_id` on `hr.holidays` becomes a regular
fields or as soon as `message_auto_subscribe` works with related/computed fields.
opw-676521
It's about 'Receipt Reference code' which gets generated when Order is
created from POS .
After this, click on 'RETURN PRODUCTS' button, the return Order doesn't
fetch the "Receipt Ref" of the origin Order, so there is no way to find
the origin order from where the return of the products done.
- Y axis : according to 12 hour or 24 hour format
- Event title : following time format in preferenced language
NB: The conversion from 'A' to 'TT' to match fullcalendar v1 should be
removed when fullcalendar is updated to v2, as the syntax will change.
See : http://fullcalendar.io/wiki/Upgrading-to-v2/
Since 3d8f7c2f, res.config support selection fields to set groups and install
modules using a selection field instead of boolean.
While the `module_*` fields are correctly casted from boolean to integers, it
was not the case with `group_*` fields.
This commit forces the conversion to get the expected field format value.
Closes#10373
Nicolas Martinelli