Warning found in logs:
2026-01-15 09:36:07,395 43 WARNING 04361-18-0-all py.warnings: /data/build/erp/dtg_hr/models/hr_employee.py:263: UserWarning: unsupported operand type(s) for "==": 'res.partner.bank()' == '54'
2026-01-15 09:36:07,468 43 WARNING 04361-18-0-all py.warnings: /data/build/erp/dtg_hr/models/hr_employee.py:263: UserWarning: unsupported operand type(s) for "==": 'res.partner.bank()' == '55'
2026-01-15 09:41:52,248 43 WARNING 04361-18-0-all odoo.addons.base.models.ir_ui_view: <b>Access Rights Inconsistency</b><br/>This view may not work for all users: some users may have a combination of groups where the elements <b><tt>&lt;div&gt;</tt></b> are displayed, but they depend on the field <b><tt>bank_account_id</tt></b> that is not accessible. You might fix this by modifying user groups to make sure that all users who have access to those elements also have access to the field, typically via group implications. Alternatively, you could adjust the “<i>groups</i>” or “<i>invisible</i>” attributes for these fields, to make sure they are always available together.<br/>Debugging information:<br/>- field “bank_account_id” is accessible for groups: &#39;hr.group_hr_user&#39; | &#39;dtg_hr.group_hr_employee_dtg_user&#39;<br/>- element “&lt;div class=&#34;d-flex&#34; invisible=&#34;not bank_account_id&#34;/&gt;” is shown in the view for groups: &#39;base.group_system&#39; | &#39;hr.group_hr_user&#39; | &#39;dtg_hr.group_hr_employee_dtg_user&#39;
2026-01-15 09:41:52,249 43 WARNING 04361-18-0-all odoo.addons.base.models.ir_ui_view: <b>Access Rights Inconsistency</b><br/>This view may not work for all users: some users may have a combination of groups where the elements <b><tt>&lt;button&gt;</tt></b> are displayed, but they depend on the field <b><tt>is_trusted_bank_account</tt></b> that is not accessible. You might fix this by modifying user groups to make sure that all users who have access to those elements also have access to the field, typically via group implications. Alternatively, you could adjust the “<i>groups</i>” or “<i>invisible</i>” attributes for these fields, to make sure they are always available together.<br/>Debugging information:<br/>- field “is_trusted_bank_account” is accessible for groups: &#39;hr.group_hr_user&#39;<br/>- element “&lt;button title=&#34;Untrust Bank Account&#34; class=&#34;icon-button button-on&#34; icon=&#34;fa-solid fa-toggle-on fa-lg&#34; type=&#34;object&#34; name=&#34;action_untrust_bank_accounts&#34; invisible=&#34;not is_trusted_bank_account&#34;/&gt;” is shown in the view for groups: &#39;base.group_system&#39; | &#39;hr.group_hr_user&#39; | &#39;dtg_hr.group_hr_employee_dtg_user&#39;
2026-01-15 09:46:07,789 43 WARNING 04361-18-0-all odoo.addons.base.models.ir_ui_view: <b>Access Rights Inconsistency</b><br/>This view may not work for all users: some users may have a combination of groups where the elements <b><tt>&lt;div&gt;</tt></b> are displayed, but they depend on the field <b><tt>bank_account_id</tt></b> that is not accessible. You might fix this by modifying user groups to make sure that all users who have access to those elements also have access to the field, typically via group implications. Alternatively, you could adjust the “<i>groups</i>” or “<i>invisible</i>” attributes for these fields, to make sure they are always available together.<br/>Debugging information:<br/>- field “bank_account_id” is accessible for groups: &#39;hr.group_hr_user&#39; | &#39;dtg_hr.group_hr_employee_dtg_user&#39;<br/>- element “&lt;div class=&#34;d-flex&#34; invisible=&#34;not bank_account_id&#34;/&gt;” is shown in the view for groups: &#39;base.group_system&#39; | &#39;hr.group_hr_user&#39; | &#39;dtg_hr.group_hr_employee_dtg_user&#39;
2026-01-15 09:46:07,790 43 WARNING 04361-18-0-all odoo.addons.base.models.ir_ui_view: <b>Access Rights Inconsistency</b><br/>This view may not work for all users: some users may have a combination of groups where the elements <b><tt>&lt;button&gt;</tt></b> are displayed, but they depend on the field <b><tt>is_trusted_bank_account</tt></b> that is not accessible. You might fix this by modifying user groups to make sure that all users who have access to those elements also have access to the field, typically via group implications. Alternatively, you could adjust the “<i>groups</i>” or “<i>invisible</i>” attributes for these fields, to make sure they are always available together.<br/>Debugging information:<br/>- field “is_trusted_bank_account” is accessible for groups: &#39;hr.group_hr_user&#39;<br/>- element “&lt;button title=&#34;Untrust Bank Account&#34; class=&#34;icon-button button-on&#34; icon=&#34;fa-solid fa-toggle-on fa-lg&#34; type=&#34;object&#34; name=&#34;action_untrust_bank_accounts&#34; invisible=&#34;not is_trusted_bank_account&#34;/&gt;” is shown in the view for groups: &#39;base.group_system&#39; | &#39;hr.group_hr_user&#39; | &#39;dtg_hr.group_hr_employee_dtg_user&#39;
2026-01-15 09:46:53,106 43 WARNING 04361-18-0-all odoo.addons.base.models.ir_model: Two fields (source_id, utm_source_id) of res.users() have the same label: Source. [Modules: None and hr_referral] 
2026-01-15 09:48:04,149 43 WARNING 04361-18-0-all odoo.addons.dtg_payment_approvals_salary: ⚠️ Rule or category not found, skipping update. 
2026-01-15 09:48:12,188 43 WARNING 04361-18-0-all odoo.addons.base.models.ir_ui_view: Error-prone use of @class in view apply_inherit_add_m2o_fields (): use the hasclass(*classes) function to filter elements by their classes 
2026-01-15 09:48:12,188 43 WARNING 04361-18-0-all odoo.addons.base.models.ir_ui_view: Error-prone use of @class in view apply_inherit_add_m2o_fields (): use the hasclass(*classes) function to filter elements by their classes 
2026-01-15 09:48:12,197 43 WARNING 04361-18-0-all odoo.addons.base.models.ir_ui_view: Error-prone use of @class in view job_detail_apply_keep_hr_officer (): use the hasclass(*classes) function to filter elements by their classes 
2026-01-15 09:49:04,721 43 WARNING 04361-18-0-all odoo.addons.base.models.ir_ui_view: <b>Access Rights Inconsistency</b><br/>This view may not work for all users: some users may have a combination of groups where the elements <b><tt>&lt;field name=&#34;l10n_be_ambulatory_insurance_notes&#34;/&gt;</tt></b> are displayed, but they depend on the field <b><tt>l10n_be_has_ambulatory_insurance</tt></b> that is not accessible. You might fix this by modifying user groups to make sure that all users who have access to those elements also have access to the field, typically via group implications. Alternatively, you could adjust the “<i>groups</i>” or “<i>invisible</i>” attributes for these fields, to make sure they are always available together.<br/>Debugging information:<br/>- field “l10n_be_has_ambulatory_insurance” is accessible for groups: &#39;hr_contract.group_hr_contract_employee_manager&#39;<br/>- element “&lt;field name=&#34;l10n_be_ambulatory_insurance_notes&#34; string=&#34;Additional Information&#34; invisible=&#34;not l10n_be_has_ambulatory_insurance&#34;/&gt;” is shown in the view for groups: &#39;hr_contract.group_hr_contract_employee_manager&#39; | &#39;dtg_hr_contract.group_hr_contract_user&#39;
2026-01-15 09:49:04,722 43 WARNING 04361-18-0-all odoo.addons.base.models.ir_ui_view: <b>Access Rights Inconsistency</b><br/>This view may not work for all users: some users may have a combination of groups where the elements <b><tt>&lt;field name=&#34;l10n_be_hospital_insurance_notes&#34;/&gt;</tt></b> are displayed, but they depend on the field <b><tt>has_hospital_insurance</tt></b> that is not accessible. You might fix this by modifying user groups to make sure that all users who have access to those elements also have access to the field, typically via group implications. Alternatively, you could adjust the “<i>groups</i>” or “<i>invisible</i>” attributes for these fields, to make sure they are always available together.<br/>Debugging information:<br/>- field “has_hospital_insurance” is accessible for groups: &#39;hr_contract.group_hr_contract_employee_manager&#39;<br/>- element “&lt;field name=&#34;l10n_be_hospital_insurance_notes&#34; string=&#34;Additional Information&#34; invisible=&#34;not has_hospital_insurance&#34;/&gt;” is shown in the view for groups: &#39;hr_contract.group_hr_contract_employee_manager&#39; | &#39;dtg_hr_contract.group_hr_contract_user&#39;
2026-01-15 09:50:30,260 43 WARNING 04361-18-0-all odoo.addons.base.models.ir_model: Two fields (source_id, utm_source_id) of res.users() have the same label: Source. [Modules: None and hr_referral] 
2026-01-15 09:51:42,756 43 WARNING 04361-18-0-all odoo.addons.base.models.ir_model: Two fields (source_id, utm_source_id) of res.users() have the same label: Source. [Modules: None and hr_referral] 
2026-01-15 09:51:57,764 43 WARNING 04361-18-0-all odoo.addons.base.models.ir_model: Two fields (source_id, utm_source_id) of res.users() have the same label: Source. [Modules: None and hr_referral] 
2026-01-15 09:52:17,335 43 WARNING 04361-18-0-all odoo.addons.base.models.ir_model: Two fields (sale_partner_name, partner_name) of helpdesk.ticket() have the same label: Customer Name. [Modules: dtg_helpdesk_customer_experience and helpdesk] 
2026-01-15 09:52:17,453 43 WARNING 04361-18-0-all odoo.models: method helpdesk.ticket._check_action_plan_on_done_stage: @constrains parameter 'code' is not writeable 
2026-01-15 09:52:19,584 43 WARNING 04361-18-0-all odoo.addons.base.models.ir_model: Two fields (source_id, utm_source_id) of res.users() have the same label: Source. [Modules: None and hr_referral] 
2026-01-15 09:52:27,226 43 WARNING 04361-18-0-all odoo.addons.base.models.ir_model: Two fields (source_id, utm_source_id) of res.users() have the same label: Source. [Modules: None and hr_referral] 
2026-01-15 09:52:31,571 43 WARNING 04361-18-0-all odoo.addons.base.models.ir_model: Two fields (source_id, utm_source_id) of res.users() have the same label: Source. [Modules: None and hr_referral] 
2026-01-15 09:52:57,461 43 WARNING 04361-18-0-all odoo.addons.base.models.ir_model: Two fields (source_id, utm_source_id) of res.users() have the same label: Source. [Modules: None and hr_referral] 
2026-01-15 09:53:01,031 43 WARNING 04361-18-0-all odoo.addons.base.models.ir_model: Two fields (source_id, utm_source_id) of res.users() have the same label: Source. [Modules: None and hr_referral] 
2026-01-15 09:53:04,138 43 WARNING 04361-18-0-all odoo.addons.base.models.ir_model: Two fields (source_id, utm_source_id) of res.users() have the same label: Source. [Modules: None and hr_referral] 
2026-01-15 09:53:07,688 43 WARNING 04361-18-0-all odoo.addons.base.models.ir_ui_view: <b>Access Rights Inconsistency</b><br/>This view may not work for all users: some users may have a combination of groups where the elements <b><tt>&lt;div&gt;</tt></b> are displayed, but they depend on the field <b><tt>bank_account_id</tt></b> that is not accessible. You might fix this by modifying user groups to make sure that all users who have access to those elements also have access to the field, typically via group implications. Alternatively, you could adjust the “<i>groups</i>” or “<i>invisible</i>” attributes for these fields, to make sure they are always available together.<br/>Debugging information:<br/>- field “bank_account_id” is accessible for groups: &#39;hr.group_hr_user&#39; | &#39;dtg_hr.group_hr_employee_dtg_user&#39;<br/>- element “&lt;div class=&#34;d-flex&#34; invisible=&#34;not bank_account_id&#34;/&gt;” is shown in the view for groups: &#39;base.group_system&#39; | &#39;hr.group_hr_user&#39; | &#39;dtg_hr.group_hr_employee_dtg_user&#39;
2026-01-15 09:53:11,144 43 WARNING 04361-18-0-all odoo.addons.base.models.ir_model: Two fields (source_id, utm_source_id) of res.users() have the same label: Source. [Modules: None and hr_referral] 
2026-01-15 09:53:15,712 43 WARNING 04361-18-0-all odoo.addons.base.models.ir_model: Two fields (currency_payment_amount, payment_amount) of receipt.details.report() have the same label: Payment Amount. [Modules: dtg_sale_report and dtg_sale_report] 
2026-01-15 09:53:17,929 43 WARNING 04361-18-0-all odoo.modules.loading: The models ['bad.debt.report.data', 'optimized.sale.resale.th.data'] have no access rules in module dtg_sale_report, consider adding some, like:
2026-01-15 09:53:21,408 43 WARNING 04361-18-0-all odoo.addons.base.models.ir_model: Two fields (source_id, utm_source_id) of res.users() have the same label: Source. [Modules: None and hr_referral] 
2026-01-15 09:53:27,233 43 WARNING 04361-18-0-all odoo.addons.base.models.ir_model: Two fields (source_id, utm_source_id) of res.users() have the same label: Source. [Modules: None and hr_referral]