| Created Date | Type | Name | Commit Description | State | Age | Up Time | Life Time | Action |
|---|---|---|---|---|---|---|---|---|
|
open
[UPG] to_fleet_driver: upgrade for v15
|
[FIX] to_employee_documents: dead test due to recent changes in to_fleet_driver | Killed | Not finished | ||||
|
|
open
[UPG] to_fleet_driver: upgrade for v15
|
[FIX] to_employee_documents: dead test due to recent changes in to_fleet_driver | Killed | |||||
|
|
open
[UPG] to_fleet_driver: upgrade for v15
|
[UPG] to_fleet_driver: upgrade for v15 This upgrade simplifies the modules by removing the license model and license class model. The module employee document is integrated for license management. 1. `driver.license.class` is now replaced with `employee.document.type` with `type` `driver_license` 2. `fleet.driver.license` is now `employee.document` | Killed | |||||
|
|
open
[UPG] to_fleet_driver: upgrade for v15
|
[UPG] to_fleet_driver: upgrade for v15 This upgrade simplifies the modules by removing the license model and license class model. The module employee document is integrated for license management. 1. `driver.license.class` is now replaced with `employee.document.type` with `type` `driver_license` 2. `fleet.driver.license` is now `employee.document` | Killed | |||||
|
|
open
[UPG] to_fleet_driver: upgrade for v15
|
[UPG] to_fleet_driver: upgrade for v15 This upgrade simplifies the modules by removing the license model and license class model. The module employee document is integrated for license management | Killed | Not started | Not finished | |||
|
|
merged
[MISC] [15.0] to_base: remove unsed code
|
[MISC] to_base: remove unsed code | Failed | |||||
|
|
merged
[UPG] viin_fleet: upgrade for v15
|
[IMP] to_fleet_load_params: various improvement Instead of define standard volumes/weight for each and every vehicle, this commit allow to define them for the model it self, then the vehicle will take that information as default | Killed | |||||
|
|
merged
[UPG] viin_fleet: upgrade for v15
|
[UPG] to_fleet_accounting: upgrade for v15 | Killed | Not started | Not finished | |||
|
|
merged
[UPG] viin_fleet: upgrade for v15
|
[UPG] viin_fleet: upgrade for v15 | Killed | |||||
|
|
merged
[UPG] viin_fleet: upgrade for v15
|
[UPG] viin_fleet: upgrade for v15 | Killed | Not started | Not finished | |||
|
|
merged
[UPG] viin_fleet: upgrade for v15
|
[UPG] viin_fleet: upgrade for v15 | Killed | Not started | Not finished | |||
|
|
merged
[UPG] viin_fleet: upgrade for v15
|
[UPG] viin_fleet: upgrade for v15 | Killed | |||||
|
|
merged
[IMP] [15.0] to_base: add demo data, incl. Viindoo
|
[FIX] viin_base_state_group: change test value to avoid dead in to_base | Killed | |||||
|
|
merged
[FIX][15.0] to_sales_stock_schedule: avoid losing cool feature call merge move of odoo
|
[FIX] to_sales_stock_schedule: avoid losing cool feature call merge move of odoo -Before this commit, try configurate exactly the same in odoo commit id : 3fd28250817d7201f76061886dbfaa3d13c1587e and we will have problem are by default odoo will merge move of same product for us but because in this module we ovveride the domain to always add [('scheduled_date', '=', self.date)] then this will lead to moves created not merge in the move that have same characteristic. -Also this would help fix merge upstream PR https://github.com/Viindoo/odoo/pull/842 -Note in v16 we already do this | Killed | |||||
|
|
merged
[FIX] to_sales_stock_schedule: avoid cool feature call merge move of odoo
|
[FIX] to_sales_stock_schedule: avoid cool feature call merge move of odoo -Before this commit, try configurate exactly the same in odoo commit id : 3fd28250817d7201f76061886dbfaa3d13c1587e and we will have problem are by default odoo will merge move of same product for us but because in this module we ovveride the domain to always add [('scheduled_date', '=', self.date)] then this will lead to moves created not merge in the move that have same characteristic. -Also this would help fix merge upstream PR https://github.com/Viindoo/odoo/pull/842 -Note in v16 we already do this | Killed | Not started | Not finished | |||
|
|
merged
[FIX][15.0] to_base : fix due to new merged upstream ... again
|
[FIX] to_base : fix due to new merged upstream ... again -Odoo has new PR pull/105532 which fix the case where a module is missing from database (ex : we delete it in the machine) then they expect the icon will fallback to the icon of base module which is currently correct but for base module, its icon is from our branding so it failed the test 'test_missing_module_icon' because base module has branding icon while 'missing' module has original base module icon. -Why is that? it turn out to be the computation of method '_get_icon_image' where we have this line https://github.com/odoo/odoo/blob/c68df402703c67becc289eb992af64dfd007e3eb/odoo/addons/base/models/ir_module.py#L274 which then eventually go to this line https://github.com/odoo/odoo/blob/c68df402703c67becc289eb992af64dfd007e3eb/odoo/modules/module.py#L343 which will execute method 'get_module_resource' in the original version not from our overriden because it not something like 'modules.module.get_module_resource' -Solution: override the method 'get_module_icon_path' to replace 'get_module_resource' with 'get_viin_brand_resource_path' | Killed | |||||
|
|
closed
[FIX][15.0] einvoice*: backport fix from v16
|
[FIX] einvoice*: backport fix from v16 -Backport from https://github.com/Viindoo/tvtmaaddons/pull/10203/commits/fb2ed13b37fd3e8d9916ac72f91918517ba1ad12 | Killed | Not finished | ||||
|
|
merged
[IMP] [15.0] to_base: add demo data, incl. Viindoo
|
[IMP] to_base: add demo data, incl. Viindoo | Killed | |||||
|
|
merged
Merged from 14 240130 01
|
Merge remote-tracking branch 'origin/14.0' into 15.0 | Killed | Not started | Not finished | |||
|
|
merged
[FWD][15.0][MISC+FIX] to_hr_payroll: use payroll localization category instead localization
|
[MISC] l10n_vn_viin_hr_payroll: handle conflict | Killed | Not started | Not finished | |||
|
|
merged
[FIX][15.0] to_hr_expense_employee_advance: fix due to new merge upstream
|
[FIX] to_hr_expense_employee_advance: fix due to new merge upstream The commit of odoo 230e5beba518c7bfdaedbf4587e25e20c490d4e8 add expense_sheet_id (o2m) in account.move . We both know that if 'default_*' existed in model creation, it will try to assign value for it, so it mean assign 'expense_sheet_id': 1 which is wrong because 'expense_sheet_id' is o2m fields, hence we remove the context out of self to ensure nothing wrong gonna happen. We just create entry so no need to change from 'expense_sheet_id' to 'viin_expense_sheet_id' | Killed | Not started | Not finished | |||
|
|
merged
[FIX][15.0] to_hr_expense_employee_advance: fix due to new merge upstream
|
Update to_hr_expense_employee_advance/wizard/account_advance_payment_register.py | Killed | |||||
|
|
merged
[FIX][15.0] to_hr_expense_employee_advance: fix due to new merge upstream
|
[FIX] to_hr_expense_employee_advance: fix due to new merge upstream The commit of odoo 230e5beba518c7bfdaedbf4587e25e20c490d4e8 add expense_sheet_id (o2m) in account.move . We both know that if 'default_*' existed in model creation, it will try to assign value for it, so it mean assign 'expense_sheet_id': 1 which is wrong because 'expense_sheet_id' is o2m fields, hence we remove the context out of self to ensure nothing wrong gonna happen. We just create entry so no need to change from 'expense_sheet_id' to 'viin_expense_sheet_id' | Killed | |||||
|
|
merged
[FWD][15.0][I18n] to_hr_payroll: fix typo
|
[I18n] to_hr_payroll: fix typo Forward-Port-Of: #10135 | Killed | |||||
|
|
merged
[MISC][15.0] to_hr_expense: rename field as odoo have the same but different type
|
[MISC] to_hr_expense: rename field as odoo have the same but different type -New PR merge upstream from v15 https://github.com/Viindoo/odoo/pull/833 with latest odoo commit 230e5beba518c7bfdaedbf4587e25e20c490d4e8 has add a field call 'expense_sheet_id' (one2many) in module sale_expense, we have this field but with type is many2one. -So there are a few cases here: Case 1: Customers using odoo 15 and have latest code from odoo. If they buy and install to_hr_expense, expense_sheet_id will be changed to many2one, expense_sheet_id one2many field will no longer exist -> this is really bad because it will definitely cause errors. Case 2: The customer has purchased the to_hr_expense module without the latest code from odoo 15, the customer's server (not yet installed sale_expense) updates the latest code from odoo 15, then install the sale_expense field, the expense_sheet_id field is still only many2one defined by the to_hr_expense module (tested twice but still dont get it why it still many2one, well never mind) ==>>>>> With both 2 cases, this commit will always cover: we change 'expense_sheet_id' to 'viin_expense_sheet_id' (just like we did when upgrade to 16) , and of course change the related logic, add migration script to change the field name (change in ir_model_fields table and rename column). ***NOTE: - This commit also remove some redundant code and when forward it to v16/master + only change the code which has been removed in the init file (the pre_init_hook) -Only notify the customer to get the latest and upgrade module and they will good to go. | Killed | |||||
|
|
merged
[MISC][15.0] to_hr_expense: rename field as odoo have the same but different type
|
[MISC] to_hr_expense: rename field as odoo have the same but different type -New PR merge upstream from v15 https://github.com/Viindoo/odoo/pull/833 with latest odoo commit 230e5beba518c7bfdaedbf4587e25e20c490d4e8 has add a field call 'expense_sheet_id' (one2many) in module sale_expense, we have this field but with type is many2one. -So there are a few cases here: Case 1: Customers using odoo 15 and have latest code from odoo. If they buy and install to_hr_expense, expense_sheet_id will be changed to many2one, expense_sheet_id one2many field will no longer exist -> this is really bad because it will definitely cause errors. Case 2: The customer has purchased the to_hr_expense module without the latest code from odoo 15, the customer's server (not yet installed sale_expense) updates the latest code from odoo 15, then install the sale_expense field, the expense_sheet_id field is still only many2one defined by the to_hr_expense module (tested twice but still dont get it why it still many2one, well never mind) ==>>>>> With both 2 cases, this commit will always cover: we change 'expense_sheet_id' to 'viin_expense_sheet_id' (just like we did when upgrade to 16) , and of course change the related logic, add migration script to change the field name (change in ir_model_fields table and rename column). ***NOTE: - This commit also remove some redundant code and when forward it to v16/master + only change the code which has been removed in the init file (the pre_init_hook) -Only notify the customer to get the latest and upgrade module and they will good to go. | Killed | Not started | Not finished | |||
|
|
merged
[FWD][15.0][MISC+FIX] to_hr_payroll: use payroll localization category instead localization
|
[MISC+FIX] to_hr_payroll: use payroll localization category instead localization -Odoo provide payroll localization at https://github.com/Viindoo/odoo/blob/cf5994705a85551737ffa8e7ffe04d4c120892ea/odoo/addons/base/data/ir_module_category_data.xml#L22 we should use that instead. This commit also fix wrong category set on action 'open_payroll_modules' Forward-Port-Of: #10120 | Killed | |||||
|
|
merged
[IMP][15.0] l10n_vn_viin_accounting_sinvoice: support product with discount percentage
|
[IMP] l10n_vn_viin_accounting_sinvoice: support product with discount percentage -Handle the todo because of customer need ref https://viindoo.com/web#id=51230&cids=1&menu_id=89&model=viin.helpdesk.ticket&view_type=form . Now sinvoice support line with discount percentage | Killed | |||||
|
|
merged
[FIX] *: conflicts with pos_sale module because module pos_sale uses UNION
|
[FIX] *: conflicts with pos_sale module because module pos_sale uses UNION | Killed | |||||
|
|
merged
[FIX] *: conflicts with pos_sale module because module pos_sale uses UNION
|
[FIX] *: conflicts with pos_sale module because module pos_sale uses UNION | Killed | Not started | Not finished | |||
|
|
merged
[FIX] *: conflicts with pos_sale module because module pos_sale uses UNION
|
[FIX] *: conflicts with pos_sale module because module pos_sale uses UNION | Killed | Not started | Not finished | |||
|
|
merged
[FWD][15.0][FIX] to_hr_timesheet_approval: fix auto approve
|
[FIX] to_hr_timesheet_approval: fix auto approve Forward-Port-Of: #10117 | Killed | |||||
|
|
merged
[MISC][15.0] to_hr_expense: rename field as odoo have the same but different type
|
[MISC] to_hr_expense: rename field as odoo have the same but different type -New PR merge upstream from v15 https://github.com/Viindoo/odoo/pull/833 with latest odoo commit 230e5beba518c7bfdaedbf4587e25e20c490d4e8 has add a field call 'expense_sheet_id' (one2many) in module sale_expense, we have this field but with type is many2one. -So there are a few cases here: Case 1: Customers using odoo 15 and have latest code from odoo. If they buy and install to_hr_expense, expense_sheet_id will be changed to many2one, expense_sheet_id one2many field will no longer exist -> this is really bad because it will definitely cause errors. Case 2: The customer has purchased the to_hr_expense module without the latest code from odoo 15, the customer's server (not yet installed sale_expense) updates the latest code from odoo 15, then install the sale_expense field, the expense_sheet_id field is still only many2one defined by the to_hr_expense module (tested twice but still dont get it why it still many2one, well never mind) ==>>>>> With both 2 cases, this commit will always cover: we change 'expense_sheet_id' to 'viin_expense_sheet_id' (just like we did when upgrade to 16) , and of course change the related logic, add migration script to change the field name (change in ir_model_fields table and rename column). ***NOTE: - This commit also remove some redundant code and when forward it to v16/master + only change the code which has been removed in the init file (the pre_init_hook) -Only notify the customer to get the latest and upgrade module and they will good to go. | Killed | |||||
|
|
merged
[FIX][15.0] viin_pos_refund: pos order might have 2 line same product but different price
|
[FIX] viin_pos_refund: pos order might have 2 line same product but different price -Step to reproduce: create a pos order with 2 line of same product, first product we set the default price as it currently, the second one we set different price -> Confirm -> create invoice -> Go to pos ui to refund -> Singleton error happen -Solution: beside filter using product_id, we also filter using price_unit. In case pos user not changing the price but add discount then this filtered is still correct. | Killed | |||||
|
|
merged
[FIX][15.0] viin_pos_refund: pos order might have 2 line same product but different price
|
[FIX] viin_pos_refund: pos order might have 2 line same product but different price -This will cause singleton and we can not create refund inv | Killed | Not started | Not finished | |||
|
|
merged
[FIX][15.0] viin_pos_refund: pos order might have 2 line same product but different price
|
[FIX] viin_pos_refund: pos order might have 2 line same product but different price -This will cause singleton and we can not create refund inv | Killed | Not started | Not finished | |||
|
|
merged
[FWD][15.0][FIX] l10n_vn_viin_stock_reports_s11dn_xlsx: fix runbot
|
[FIX] l10n_vn_viin_stock_reports_s11dn_xlsx: fix runbot Forward-Port-Of: #10037 | Killed | Not started | Not finished | |||
|
|
merged
[FWD][15.0][FIX] viin_hr_overtime: fix test new year
|
[FIX] viin_hr_overtime: fix test new year Forward-Port-Of: #10034 | Killed | Not started | Not finished |
