Thursday, February 3, 2022
8 changes · master
Resolved issues and error corrections
Public and portal visitors can now access event ticket information where existing rules already allow it. This prevents website event pages and single app builds from crashing when ticket descriptions are loaded.
Original PR description
There isn't `ir.model.access` on `event.event.ticket` for public and portal users, but there is already the `ir.rule` to check the access. It causes an issue now because, since https://github.com/odoo/odoo/pull/82896, the `description` field of `event.event.ticket` isn't prefetch anymore by the sudoed `event_registrations_open` compute (that fill the cache with ticket data in sudo). It crashes single app build: https://runbot.odoo.com/runbot/build/12473674
This change ensures the web interface has the translation support it needs when showing a screen-blocking message. It prevents a small internal dependency issue that could affect the reliability of this user interface behavior.
Original PR description
This commit adds the "localization" dependency to the ui_service. The BlockUi component used by ui_service uses the _t function added by the localization service. 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
Users who jump across multiple gamification ranks will now receive only the relevant final rank notification instead of separate emails for each intermediate rank. This reduces unnecessary email noise, especially during new database setup when the administrator starts with enough karma to skip several ranks.
Original PR description
Purpose ======= When a user changes more than one rank at the time, avoid sending emails for every intermediate rank. This is particularly annoying when creating a new database, since the admin starts with 2500 karma and is sent 4 emails for each intermediate rank. Task-2746929
Starting a manufacturing work order will no longer automatically suggest producing the full manufacturing order quantity. This helps operators notice when an earlier step produced less than planned, reducing the risk of carrying forward an incorrect quantity.
Original PR description
In 9f7e6d2bb6ae0a6b0257edf26a5aa069cd00d78e , when start a workorder, we always suggest the qty to produce to be the full qty to produce on MO. If the previous WO produced less than the full qty to produce on MO, user won't aware of that when start the WO. We revert it in this committ Task-2678388 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes an issue that could block or incorrectly validate new bank account setup in the accounting wizard. Company bank accounts can now be linked to the expected journal even when the related company partner has no company set, reducing setup errors for users.
Original PR description
When trying to set up a new bank account using the bank account wizard, there is an issue with the check company on the linked_journal_id field. The check will make sure that the company on that field is either false or the same as the company on the record. But with a recent change in 68f4534aa5d0c6d900128c93f5a2289c06bb3d14 the bank account company_id will be the one from the linked partner. As the partners for companies have an empty company_id, this check does not make a lot of sense anymore, as it would be wrong in most cases. (We expect a journal with the currently selected company, but the bank account will in most cases have an empty company_id) -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Fixes an issue in Mail where clicking a mention or link inside the preview of a message being replied to could trigger an error. Users can now interact with those preview links without disrupting the reply flow.
Original PR description
When clicking on a mention (or a link) within the preview of the message we're replying to, there was a traceback because we tried to update a component which has already been deleted. task-id: 2747321 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
Starting a work order will no longer automatically suggest producing the full manufacturing order quantity. This helps operators notice when an earlier step produced less than planned, reducing the risk of carrying an incorrect quantity into the next operation.
Original PR description
In c3a89338986413a59143b0240c7dbf6b68d19e69 , when start a workorder, we always suggest the qty to produce to be the full qty to produce on MO. If the previous WO produced less than the full qty to produce on MO, user won't aware of that when start the WO. We revert it in this commit. Task-2678388
This update fixes a bug in the timesheet grid to help ensure timesheet information behaves as expected. It matters because employees and managers rely on accurate timesheet entry and review for project tracking and billing.