Thursday, March 5, 2020
26 changes · master
New functionality added to Odoo
Project templates can now carry key service, field service, worksheet, quotation, materials, and forecasting settings into newly created projects. Template-only records are also kept out of operational reports and selection fields where they do not belong, reducing setup errors and cleaner reporting.
Original PR description
Purpose
=======
Same purpose as PR : https://github.com/odoo/odoo/pull/45418
Specifications
==============
- Fields to be copied in enterprise from a template to a project :
is_fsm, allow_material, allow_quotations, allow_worksheets, worksheet_template_id,
allow_forecast
- Invisible fields in enterprise on project.project form (templates):
Planning stat button, Tickets stat button
- Invisible fields in enterprise on project.task form :
planned_date_begin, planned_date_end, Products stat button, Invoices stat button,
Quotations stat button, Planning overlap alert, worksheet stat button
- Add demo data
Task-1975084
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prEnhancements to existing features
The email campaign overview cards now have a more consistent bottom section that matches other Odoo screens. User avatars are shown as round images, making the interface look cleaner and more polished.
Original PR description
This commit improves the bottom section of the mailing.mailing kanban view to make it follow other kanban views structure. It makes the user avatar on the mailing.mailing kanban display in a round shape instead of a square (with border-radius). LINKS Task ID 2207856 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
Resolved issues and error corrections
This update removes leftover support for an old way of loading Odoo add-ons. It keeps the codebase aligned with the current supported import method, reducing maintenance risk without changing normal user workflows.
Original PR description
Historically, it was possible to import addons via a naked import. It is no more possible since 9e1f13bac, since that commit, the only possible way to import odoo addons is via the `import odoo.addons' prefix.
Miscellaneous changes
-- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#46971 Forward-Port-Of: odoo/odoo#46892
Original PR description
-- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#46971 Forward-Port-Of: odoo/odoo#46892
Website editors can now round corners on elements that have a background color even when no border is applied. They can also choose common border styles like solid, dashed, dotted, or double, making page design options more flexible and consistent.
Original PR description
Previously, the border radius option was only available when there was a border width, but in some cases you want no border, a background color, and still have rounded corners. This commit makes the option available when there is either a border OR a background color. This commit also adds an option to choose the border style between solid, dashed, dotted and double. The other styles have been left out as they look very different browser to browser and are not very useful. task-2195429
The Apps and modules screen now includes a search panel to make it easier to see and filter available or installed apps. This helps users find relevant modules faster and reduces the chance of overlooking useful functionality.
Original PR description
Purpose ======= The current kanban view is messy. It is difficult to identify which apps are installed or not. The user can completely miss a module that might have interested him. A search panel would make things way more readable. TaskID: 2181557 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 website shop confirmation text was rewritten to read more naturally and logically. This improves the customer checkout experience by making the information shown after purchase easier to understand.
Original PR description
The sentence was a bit odd before this commit. After this commit it reads easier and it is more logical. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The debug menu now includes direct links to view access rights and record rules. This helps administrators and support teams investigate permission issues faster without navigating through multiple settings screens.
Original PR description
PURPOSE Debugging access issues can quickly be a pain. The goal is to allow to easily debug an access rights issue from the debug tools. SPECIFICATION In the debug tools, add the following two new items: - View Access Rights - View Record Rules -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The Sales module now uses a clearer name for the email template that adds online sign and pay buttons to quotations. This makes the template easier for teams to identify and manage without changing customer-facing sales behavior.
Original PR description
PURPOSE The purpose of this commit to change the name of view in xml file in slale module. SPECIFICATIONS In Sale, there is a view called oezirhgoi which adds the sign and pay online buttons so we rename the templte "view and pay". LINKS PR#46954 Task:2196751
New user account logins are now saved in lowercase by default, reducing sign-in issues caused by accidental or random capitalization. Existing accounts with mixed-case logins remain supported because authentication checks both the entered login and its lowercase version.
Original PR description
The account creation and verification was case sensitive on the login and could cause problems for users to connect (i.e. when a server administration creates account with random uppercases). With this commit, newly created accounts will have a lowercase login and the authentication tests both the user given login (preserving the case) and lowercase counterpart to ensure backward compatibility with previously created mixcase accounts plus ease the connection for all new accounts. Task: 34047
The barcode app has been updated with a cleaner, more mobile-friendly interface and easier ways to adjust quantities directly from barcode lines. Warehouse users can also change source or destination locations from the barcode screen and start returns more easily, reducing reliance on barcode scanners and speeding up stock operations.
Original PR description
- Made visual changes in the barcode view; - Remade the line form view for barcode app; - Add buttons to increase transfer quantity on barcode line; - Add the possibility to click on location summary to change the move lines' location directly from the barcode view; - A little ref. in xml/js files. task-2123726
The app/module list now includes a search panel to make it easier to see and filter available or installed apps. This helps users find relevant apps more quickly and reduces the chance of overlooking useful functionality.
Belgian payroll now supports full-time credit time, including visible zero-value credit time days on payslips. The update also improves payroll accuracy for employees who start or end contracts mid-month, reducing wages and benefits based on actual worked time.
Original PR description
Make possible to take a credit time full time Further more, the credit time days appears on the payslip (at 0 € but it must be visible in the payslip) In the wizard of credit time add a m2o to work entry type: - not required - filled by default with credit time - when the work entries are generated, use this work entries to show credit time off - if not visible show days of in grey TASK-ID: 2145813
This fix gives Odoo fields safe default labels when they are inspected outside the normal application environment. It prevents a rare infinite loop that could occur in developer or diagnostic scenarios, improving stability without changing everyday business workflows.
Original PR description
From python code, import a module class and print one of its field, it creates an infinite recursion due to `model_name` and `name` field attributes being accessed by `__str__` but only being set when accessing a model through the environment. This commit provide a default values for the field name and the field model name to prevent that infinite recursion.
CRM lead forms now rely on standard layout styling so longer field labels display more reliably. This reduces visual breakage in the form and makes the interface easier to maintain over time.
CRM demo records were corrected so lead conversations show messages from the right contact rather than another user. This makes sample CRM data clearer and avoids confusion when evaluating or demonstrating lead communication history.
Original PR description
Purpose Clean CRM demo data. Specifications In the chatter of few leads, there are wrong entries in the discussion due to incorrect demo data. Goal of this commit is to improve incorrect demo data. LINKS PR #44253 Task 2180228
An internal setup test was corrected so it runs under the intended schedule instead of running all the time. This helps prevent unnecessary test failures caused by moved documentation pages, improving reliability for ongoing development.
Original PR description
The tag "nightly" is not an actual thing, so the test gets run all the time, and since the taxcloud page has been moved it now breaks. Replace by the proper tag.
This fixes an internal Helpdesk test so it only runs in the intended test schedule. It prevents unrelated website documentation changes from causing unnecessary test failures, helping keep development checks stable.
Original PR description
The tag "nightly" is not an actual thing, so the test gets run all the time, and since the taxcloud page has been moved it now breaks. Replace by the proper tag.
A horizontal scroll appears on medium to large screen sizes in the form's chatter sidebar (e.g. between 1534px and 1619px, when all modules are installed). This commit restores the padding set by Bootstrap for `.nav-link` elements instead of a fraction of the grid gutter's (?) width then applying slightly smaller padding. Task ID: 2193950 Forward-Port-Of: odoo/odoo#46854 Forward-Port-Of: odoo/odoo#44932
Original PR description
A horizontal scroll appears on medium to large screen sizes in the form's chatter sidebar (e.g. between 1534px and 1619px, when all modules are installed). This commit restores the padding set by Bootstrap for `.nav-link` elements instead of a fraction of the grid gutter's (?) width then applying slightly smaller padding. Task ID: 2193950 Forward-Port-Of: odoo/odoo#46854 Forward-Port-Of: odoo/odoo#44932
Forward-Port-Of: odoo/odoo#46887
Original PR description
Forward-Port-Of: odoo/odoo#46887
Update the account_invoice_extract module to work with newer version of pdf.js ( odoo/odoo#40917 ) task-2198662 Forward-Port-Of: odoo/enterprise#9017
Original PR description
Update the account_invoice_extract module to work with newer version of pdf.js ( odoo/odoo#40917 ) task-2198662 Forward-Port-Of: odoo/enterprise#9017
Call read_group on planning slot, grouping by employee with `start_datetime` in the domain and the value being a datetime object. e.g. ```python self.env['planning.slot'].read_group( [('start_datetime', '>', datetime.now())], ['employee_id'], ['employee_id'], ) ``` The group_expand method crashes because it assumes the value is a string whereas it can be a date or datetime object. Note: a datetime object is an instance of date ```python from datetime import date, dateti
Original PR description
Call read_group on planning slot, grouping by employee with `start_datetime`
in the domain and the value being a datetime object.
e.g.
```python
self.env['planning.slot'].read_group(
[('start_datetime', '>', datetime.now())],
['employee_id'],
['employee_id'],
)
```
The group_expand method crashes because it assumes the value is a string
whereas it can be a date or datetime object.
Note: a datetime object is an instance of date
```python
from datetime import date, datetime
dt = datetime.now()
isinstance(dt, date)
>>>True
```
Forward-Port-Of: odoo/enterprise#9009A horizontal scroll appears on medium to large screen sizes in the documents' chatter sidebar. This commit fixes it by correctly converting unapplied `right` CSS rules to their equivalent `margin-right` values. Also, it gives a little more space to the chatter by raising its width from 450px to 525px. Task ID: 2193950 Forward-Port-Of: odoo/enterprise#9005 Forward-Port-Of: odoo/enterprise#8984
Original PR description
A horizontal scroll appears on medium to large screen sizes in the documents' chatter sidebar. This commit fixes it by correctly converting unapplied `right` CSS rules to their equivalent `margin-right` values. Also, it gives a little more space to the chatter by raising its width from 450px to 525px. Task ID: 2193950 Forward-Port-Of: odoo/enterprise#9005 Forward-Port-Of: odoo/enterprise#8984
Steps to reproduce the bug: - Let's consider an asset type AT with method_number = 5 - Create an asset A and change the method_number to 4 - Export A in a csv file F (with Number of depreciations in the exported fields) - Import F Bug: The method number was equal to 5 instead of 4. opw:2192296 Forward-Port-Of: odoo/enterprise#8551 Forward-Port-Of: odoo/enterprise#8488
Original PR description
Steps to reproduce the bug: - Let's consider an asset type AT with method_number = 5 - Create an asset A and change the method_number to 4 - Export A in a csv file F (with Number of depreciations in the exported fields) - Import F Bug: The method number was equal to 5 instead of 4. opw:2192296 Forward-Port-Of: odoo/enterprise#8551 Forward-Port-Of: odoo/enterprise#8488
Steps to reproduce the bug: - Install Purchase, Sales (Inventory) - Create Company A, Company B (Mitchell Admin has access to both) - In both companies: General Settings/check Inter-Company Transactions Synchronize sales/purchase orders - Sales Team, restrict company_id of Europe to Company A - Create a (storable) product P with Inventory/MTO route and Purchase/Vendor Company B - Create a SO in A with P, confirm - Run scheduler to trigger a PO for P - Confirm the PO Bug:
Original PR description
Steps to reproduce the bug: - Install Purchase, Sales (Inventory) - Create Company A, Company B (Mitchell Admin has access to both) - In both companies: General Settings/check Inter-Company Transactions Synchronize sales/purchase orders - Sales Team, restrict company_id of Europe to Company A - Create a (storable) product P with Inventory/MTO route and Purchase/Vendor Company B - Create a SO in A with P, confirm - Run scheduler to trigger a PO for P - Confirm the PO Bug: An access error was raised because the new SO in Company B was created with team_id = Europe. opw:2176346 Forward-Port-Of: odoo/enterprise#8804
Steps to reproduce the bug: - Install l10n_ar_reports - Go to Accounting>Reporting>Purchases VAT book - Print the report Bug: The Sales VAT book was printed opw:2197740 Forward-Port-Of: odoo/enterprise#8540 Forward-Port-Of: odoo/enterprise#8534
Original PR description
Steps to reproduce the bug: - Install l10n_ar_reports - Go to Accounting>Reporting>Purchases VAT book - Print the report Bug: The Sales VAT book was printed opw:2197740 Forward-Port-Of: odoo/enterprise#8540 Forward-Port-Of: odoo/enterprise#8534