You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Tree: 80270603a3

12.0

12.0-beesdoo-easymycoo-fix

12.0-beesdoo_account-imp-invoice-negative-amount

12.0-beesdoo_base-fix-group-force-barcode

12.0-beesdoo_purchase-adapt-product-purchase-selling-price

12.0-beesdoo_shift-fix-action_worker

12.0-beesdoo_shift-search-default-gb-type

12.0-fix-b_emc-checkbox

12.0-fix-b_s_attendance-shift_does_not_exists

12.0-fix-b_shift-trad

12.0-fix-beesdoo_shift-res_partner

12.0-fix-cooperator_status

12.0-macavrac-prod

12.0-openupgrade

12.0-pog-filter_product_on_supplier

12.0-pos_keyboard

12.0-posorder_amount_by_year

12.0-pre-commit-target

12.0-sc-effective-sale-price

12.0-supplier_margin

12.0-tasmeilleurtemps

20181114_155

9.0

9.0-bees-highlight_task_template

9.0-beesdoo_shift-add-search-filter

9.0-docker

9.0-hide-countdown-date-unsuscribed

9.0-po-add-partner

9.0-s0055-beescard-remy-vincent

9.0-shift6-welcome_screen-tfr

9.0_warn_on_oversubscribe2

12.0-2020-05-11.00

12.0-2020-05-12.00

12.0-2020-05-12.01

12.0-2020-06-26.00

12.0-2020-06-26.01

12.0-2020-08-19.00

12.0-2020-08-26.00

12.0-2020-08-27.00

12.0-2020-09-06.00

12.0-2020-09-20.00

12.0-2020-09-27.00

9.0-2020-02-19.00

9.0-2020-02-24.00

9.0-2020-04-08.00

v1.0-2017-02-26

v1.1-2017-05-08

v1.1-2017-07-05

v1.2-2018-12-01

v1.2.1-2018-12-02

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '80270603a3'

${ noResults }

cooperative-market/beesdoo_shift

History

Rémy Taymans 80270603a3 [FIX] b_shift: Properly resigning worker This fix the case where a worker is unsubscribed from a shift where he is supercooperator. In the function unsubscribed_from_today, when removing the supercoop, the field is_regular was also set to False. I seams that this is not correct as this field is related to the worker_id not to the supercoop. Also, I found other issues as when removing a worker_id the fields is_regular and is_compensation was not reset. This let me think about other cases where worker_id is emptied, the is_regular and is_compensation would be never been reset if the programmer doesn't think to reset it. So I modified the constrains on these field in order to have these field reset properly when worker_id is changed.		5 years ago
..
data	[CHANGE] Change the computation for unsubscribed status of irregular worker	5 years ago
models	[FIX] b_shift: Properly resigning worker	5 years ago
security	[FIX] Remove wrong access right line	5 years ago
views	[FIX] b_shift: Raise error when shift not configured well	5 years ago
wizard	[FIX] fix first registration shift	5 years ago
__init__.py	[ADD] beesdoo_shift module, first version of the module to manage shifts	5 years ago
__openerp__.py	[FIX] b_shift: Properly resigning worker	5 years ago