This adds a field `supervisor_id` that aims to replace the `create_uid`
field. To prevent regressions, the old `create_uid` field is set to be a
computed field that has the same value as `supervisor_id`. This allow to
ensure that other part of the program that refer to `create_uid` as the
responsible for a purchase order will get the value of `supervisor_id`.
This new version comes with a migration script that fill the new
`supervisor_id` with the value of `create_uid` if `supervisor_id` is not
set yet.
This trick is done because the `create_uid` field is a magic field that
belongs to the ORM. This field cannot be modified in a form.
Remove date_planned and button to set date in tab delivery
Add a new field manual_date_planned
Onchange on order_line to set the first time a date planned
Force the manual_date_planned to all line at confirmation
Change the report for purchase order
[ADD] default value on picking responsible: set the create_uid as responsible (this mean the one that confirm the purchase order
When the worker has subscribed to a shift template but not yet to a
shift, the shift used to generate her next shift is the first shift
found in the shift template (so this is a shift that is attached to
another worker from the same shift template).
Now the system pays attention to not use a shift that has no start time
or end time defined.
There was an issue that shows an error message when trying to modify the
settings for shift in the website configuration.
This is due to a missing sequence in the database. I don't know why this
sequence where not present. But a simple query create it if it doesn't
exists.
Rémy Taymans
nicolasjamoulle
Thibault Francois
robinkeunen
odoo
odoo
Thibault Francois
EliseDup
EliseDup
EliseDup
Elouan Le Bars
Augustin Borsu
Manuel Claeys Bouuaert