Thursday, January 24, 2019
11 changes · master
Enhancements to existing features
Payroll entries can now use the analytic account set on an employee's contract when the salary rule does not already specify one. This helps businesses report payroll costs by employee group or department without changing existing salary rule behavior.
Original PR description
If the employee's contract has an analytic account it should be considered for the payroll. This is actually the way analytic accounts are meant to be used in the payroll, to segregate information based on specific groups of employees or departments. This does not override the default behavior, it just uses the analytic account on the contract if it has it and the salary rule doesn't. Ticket #1927941 Closes #30119
The time off process now checks for conflicting leave requests not only when dates change, but also when the employee or request status changes. This prevents a previously refused leave from being reactivated in a way that creates two leave records for the same employee on the same day.
Original PR description
Purpose ======= There is already a check triggered when we modify the start/end date. But it's still possible to: - Create a leave A - Refuse it - Create a leave B on the same day - Reset the leave A in draft state Specification ============= The test should also be done when modifying the employee or the state.
Employees who submit expenses by email now receive a confirmation when the expense is successfully recorded. Email subject parsing is also more reliable, with better product matching and currency recognition, reducing mistakes and manual corrections.
Original PR description
Task: https://www.odoo.com/web?#id=35093&view_type=form&model=project.task&action=327&menu_id=4720 Pad: https://pad.odoo.com/p/r.9efc2b24d8595bc156b5fe1088a0682e Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The Point of Sale product selection screen now supports keyboard input for number keys, Backspace, and Delete. This helps cashiers select or adjust products more quickly without relying only on touch or mouse interactions.
Original PR description
Task : https://www.odoo.com/web#id=33518&view_type=form&model=project.task&action=327&menu_id=4720 Pad : https://pad.odoo.com/p/r.71bfd6f6bb6c7192aee7883e7c7a9b3b
The Belgian salary configurator now separates standard annual leave from optional extra time off. This makes salary package choices clearer by showing annual legal leave and extra leave as distinct benefits, with the selector focused only on additional days off.
Original PR description
purpose ====== In salary configurator, improve the cusrsor to select only extra leaves. Specification ============= Specification ========== Section legal leaves: - Rename "Legal leaves" into "Extra…
purpose ====== In salary configurator, improve the cusrsor to select only extra leaves. Specification ============= Specification ========== Section legal leaves: - Rename "Legal leaves" into "Extra Time Off" - change the cursor 0 -> 15 Change the text (rmove completely old one if you go below 20) In addition to your legal leaves, you can choose any number of extra time off you want. If you worked a full time 12 months last year, you will get a total of [ 27 ] day(s) off. The amount of annual time off (legal leaves) you get depends on your work schedule in the previous year. A full-time work schedule through the 12 months of the last year will grant you 20 annual time off (legal leaves) In yearly advantages (on the right right) - Cash 4000 € - Annual Time Off 20 day(s) - Extra Time Off 7 day(s) Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The salary configurator now separates standard annual time off from optional extra time off more clearly. Employees can choose extra days with a 0 to 15 day slider, while yearly benefits show cash, annual time off, and extra time off as separate items.
Original PR description
purpose ====== In salary configurator, improve the cusrsor to select only extra leaves. Specification ============= Specification ========== Section legal leaves: - Rename "Legal leaves" into "Extra Time Off" - change the cursor 0 -> 15 Change the text (rmove completely old one if you go below 20) In addition to your legal leaves, you can choose any number of extra time off you want. If you worked a full time 12 months last year, you will get a total of [ 27 ] day(s) off. The amount of annual time off (legal leaves) you get depends on your work schedule in the previous year. A full-time work schedule through the 12 months of the last year will grant you 20 annual time off (legal leaves) In yearly advantages (on the right right) - Cash 4000 € - Annual Time Off 20 day(s) - Extra Time Off 7 day(s)
PLM approvals now keep a separate record for each approval or rejection instead of only showing the latest action. This gives teams clearer traceability on Engineering Change Orders, including dates and chatter messages, with small visual cues to show the current approval status.
Original PR description
Task:https://www.odoo.com/web#id=1819087&model=project.task&view_type=form&menu_id=4720 Pad:https://pad.odoo.com/p/r.99e765ecc1cefc870e20389618acadf9 -- each time a user approves or rejects a PLM, it should create a new approval line -- on the ECO and message logged in the chatter. This commit is related to task ID 1819087
Resolved issues and error corrections
This fix adds the automatically generated 999999 transition account to the French accounting chart template. It supports proper handling of prior-year results in France, where allocation depends on whether the result is positive or negative, reducing setup issues after migrations or new chart creation.
Original PR description
Add need to use 999999 account (auto generate), because in France the affectation depends on the result (positif or minus / 120 or 129). And it is not possible to have multi unaffected account in Odoo. https://github.com/odoo/odoo/commit/87db2ccd75a849fce4230c0736e78511d7ad8c99 @alexis-via @alnslang @qdp-odoo Pr link to : https://github.com/odoo/odoo/pull/17777 Impacted version : 9/10/Master NOTA : it seems during the Odoo migration V8 to V9, this account is not add. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix restores the website animation system to its previous behavior after a recent editor-related change made it more complex and less reliable. It also adjusts the website forum integration so animations start correctly without unnecessary checks or restarts, reducing the risk of page behavior issues and future merge conflicts.
Original PR description
* website_forum Following the new editor's merge at https://github.com/odoo/odoo/pull/29775, the website 'animation' system was 'extended' to vaguely use a 'Registry' instance instead of an object.…
* website_forum Following the new editor's merge at https://github.com/odoo/odoo/pull/29775, the website 'animation' system was 'extended' to vaguely use a 'Registry' instance instead of an object. This was however left undocumented, with a require in the middle of a file, restarting all animations when used, only used by website_forum... with more code for no reason at all, ... This commit restores the system to the way it was before and re-adapts website_forum: - No need to check if website_forum is in the DOM as it is already checked by the animation system (on top of that... the new code was checking the DOM before it was ready...). - No need of a dynamic add on a registry, this is always done before the DOM is ready, so before the animations are started. - No need to know the root instance in website forum, just use the animation as the Wysiwyg instance's parent. The goal of this commit is also to avoid useless conflicts with https://github.com/odoo/odoo/pull/29442 (that should not have had any conflict at all as totally independent of the editor task...)
The portal signature feature no longer depends on an unnecessary website editor component. This reduces the chance of loading issues after recent editor changes while keeping the portal behavior unchanged for users.
Original PR description
Following the new editor's merge at https://github.com/odoo/odoo/pull/29775, the 'web_editor.ready' module was moved to website without caring about where it was used. Fortunately the only non-website app which uses it is portal in a module which in fact does not need it. It would probably make more sense if it was in portal though (see https://github.com/odoo/odoo/pull/30409) but as an upcoming PR is about to fix those problems (https://github.com/odoo/odoo/pull/29442), this can stay in website for now.
A typo in the Project Enterprise app setup information was corrected. This ensures the app is properly installed when the Project app is used, avoiding missing functionality for users.
Original PR description
Otherwise the module is not installed when project is...