Daily updates from Odoo
Navigate
Branch
Monday, July 26, 2021
9 changes
Enhancements to existing features
Once a timesheet has been validated, any linked global time off can no longer be edited. This helps preserve approved records and prevents accidental changes after validation.
Original PR description
When a timesheet is already validated, the global time off linked to it shouldn't be editable. Task-2352428
Managers can now see pending employee time off more clearly when reviewing schedules. Unapproved time off is shown distinctly, warnings explain that time off has been requested, and time-off filters include both pending and approved requests so planning can be adjusted earlier.
Original PR description
_* = web_gantt
The purpose of the task is to inform the manager that an employee
has submitted a timeoff request and that the planning might need
to be adapted accordingly
So in this commit, done the following changes:
- non-validated time off should be displayed in grey hatched.
- adapt the timeoff warning to "Employee has requested timeoff..."
for non validated timeoff of employees in form view and popover
- "employees on time off" filter should return shifts that fall during
both non validated and validated time off
TaskId: 2485142Resolved issues and error corrections
The timesheet grid now shows the correct status bubble color when a timesheet is not yet validated. This avoids confusion by clearly distinguishing pending timesheets from validated ones.
Original PR description
Fixes the bubble color for the status bubble introduced with the PR below. Without this commit the status bubble is always green instead of blue when not validated. See odoo/enterprise#19355 Task ID: 2612062
The wording used for appointment sharing links was corrected so users see clearer, more accurate text. This helps avoid confusion when sharing or inserting calendar appointment links on the website.
Original PR description
Task ID: 2610953
Documentation and clarification updates
This update makes license information explicit across many enterprise app manifests. It helps avoid future system warnings and gives clearer legal/compliance information without changing day-to-day functionality.
Original PR description
The license is missing in most enterprise manifest so the decision was taken to make it explicit in all cases. When not defined, a warning will be triggered starting from 14.0 when falling back on the default LGPL-3.
Miscellaneous changes
With this commit, only acquirers that support validation (and not only tokenization) will be shown in the "Manage Payment Methods" modal on the portal view of subscriptions. This doesn't affect the list of acquirers shown in the payment form for subscriptions renewal. task-2494916 Community PR: https://github.com/odoo/odoo/pull/73433 Forward-Port-Of: odoo/enterprise#19764 Forward-Port-Of: odoo/enterprise#19550
Original PR description
With this commit, only acquirers that support validation (and not only tokenization) will be shown in the "Manage Payment Methods" modal on the portal view of subscriptions. This doesn't affect the list of acquirers shown in the payment form for subscriptions renewal. task-2494916 Community PR: https://github.com/odoo/odoo/pull/73433 Forward-Port-Of: odoo/enterprise#19764 Forward-Port-Of: odoo/enterprise#19550
Steps to reproduce the bug: - Go to Payroll app > Payslips > To Pay - Choose any Payslip - Go to the Accounting Information tab Problem: `”Made Payment Order ?”` field is always readonly when it should be clickable when the status is in draft or in verify according to the rule defined in the python code. It doesn't make sense to always put it in readonly in xml because it overrides the python rule : https://github.com/odoo/enterprise/blob/faf69b3de1d7fc955e3f6271fd24b901310fe5e4/hr_payr
Original PR description
Steps to reproduce the bug: - Go to Payroll app > Payslips > To Pay - Choose any Payslip - Go to the Accounting Information tab Problem: `”Made Payment Order ?”` field is always readonly when it should be clickable when the status is in draft or in verify according to the rule defined in the python code. It doesn't make sense to always put it in readonly in xml because it overrides the python rule : https://github.com/odoo/enterprise/blob/faf69b3de1d7fc955e3f6271fd24b901310fe5e4/hr_payroll/models/hr_payslip.py#L58-L59 opw-2608818 PR for V12.0: https://github.com/odoo/odoo/pull/74176 Forward-Port-Of: odoo/enterprise#19825 Forward-Port-Of: odoo/enterprise#19818
The currently existing domain to get the accounts lines in the reconciliation widget isn't working as expected. Fix it Forward-Port-Of: odoo/enterprise#19805
Original PR description
The currently existing domain to get the accounts lines in the reconciliation widget isn't working as expected. Fix it Forward-Port-Of: odoo/enterprise#19805
Before this commit the value of result['today']['success'] can be 33,33333333 %.  @tde-banana-odoo Forward-Port-Of: odoo/enterprise#19716
Original PR description
Before this commit the value of result['today']['success'] can be 33,33333333 %.  @tde-banana-odoo Forward-Port-Of: odoo/enterprise#19716