Thursday, November 7, 2019
9 changes · master
Enhancements to existing features
The technical administration menus for email and Discuss have been reorganized to make them easier to navigate. Administrators also gain direct access to notification records, improving visibility when investigating messaging activity.
The lead feedback modal now uses clearer, grammatically correct wording when partners explain why they are not interested in a lead or confirm customer contact. This improves professionalism and reduces confusion for users providing lead feedback.
Original PR description
These sentences weren't correct: Why aren't you interested **by** this lead? => Why aren't you interested **in** this lead? **Do you** have contacted the customer? => **I** have contacted the customer task-1838187 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 accounting reversal wizard now keeps track of all newly created reversal entries. This helps related processes, such as helpdesk ticket billing links, correctly connect invoice lines even when multiple reversals are created.
Original PR description
Add new move reversal line in wizard model, those new_move_ids are useful for the override in helpdesk. id=2017554 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The configuration help text now makes it clear that memory limit values must be entered in bytes. This helps first-time Odoo deployments avoid confusion and reduces the chance of incorrect server settings.
Original PR description
When you deploy Odoo for the first time, it is not explicit that you must enter a value in bytes for these specific parameters.
This change improves Odoo's internal test framework so cleanup actions run more reliably when shared test setup fails. It helps reduce leftover test data and unstable database states, making automated testing safer and more dependable for future development.
Original PR description
This commit backports bpo-24412, which allows the definition of class cleanups (addClassCleanup) similar to instance cleanups (addCleanup). This is useful for tests that override unittest's setUpClass (a LOT) and could crash during its execution: If this happens, it is possible that a bunch of crap is left in the database or even worse, the cursor becomes completely fucked; Thanks to the addClassCleanup, we can undo the damage done by the setUpClass.
The test suite has been updated so many tests no longer depend on preloaded demo data. This makes future demo data changes safer, improves test performance, and supports more flexible release and migration testing.
Original PR description
Purpose ======= This is the first huge step to improve the test suite in several ways: - Make them demo data independent, allowing to modify the demo data without having to adapt the tests depending on it. It also allows to have a beautiful + convenient demo dataset to make a demonstration, and to configure complex data in the tests to manage the corner cases. - Improve the test performances by converting them into SavepointCase. Each test will be rollbacked to it's initial state, after the setUpClass call. That way the different data are not re-created at each test for nothing. - Introduce several test classes in base/tests/common.py to launch a TransactionCase, HttpCase or SavepointCase test with an available demo user, portal user or a large set of partners. - This is the first step to tend to a rolling release process, allowing to execute the tests (or a subset of the tests) on a migrated base, for example. TaskID: 2075739
The phone calls configuration menu has been moved into the dedicated Phone / SMS technical menu. This makes administration screens easier to navigate by separating phone-related settings from Discuss, email, and mass mailing entries.
Original PR description
Purpose is to clean a bit technical menu, notably separating Discuss, Emails, Mass Mailing and Phone menu entries. Indeed there are quite a lot of menu entries and finding something is sometimes difficult. Task 2118599 Community PR odoo/odoo#39460 PR #6539
Phone call administration entries have been moved into the Phone / SMS technical menu. This makes the technical settings easier to navigate by separating phone-related items from other communication tools like Discuss, Email, and Mass Mailing.
Original PR description
Purpose is to clean a bit technical menu, notably separating Discuss, Emails, Mass Mailing and Phone menu entries. Indeed there are quite a lot of menu entries and finding something is sometimes difficult.
This update makes many accounting and payment tests independent from demo data, so demo examples can change without breaking validation. It also improves test reliability and performance by reusing prepared test data more efficiently, supporting faster and safer future releases.
Original PR description
Purpose ======= This is the first huge step to improve the test suite in several ways: - Make them demo data independent, allowing to modify the demo data without having to adapt the tests depending on it. It also allows to have a beautiful + convenient demo dataset to make a demonstration, and to configure complex data in the tests to manage the corner cases. - Improve the test performances by converting them into SavepointCase. Each test will be rollbacked to it's initial state, after the setUpClass call. That way the different data are not re-created at each test for nothing. - Introduce several test classes in base/tests/common.py to launch a TransactionCase, HttpCase or SavepointCase test with an available demo user, portal user or a large set of partners. - This is the first step to tend to a rolling release process, allowing to execute the tests (or a subset of the tests) on a migrated base, for example. TaskID: 2075739