Wednesday, April 12, 2023
46 changes · master
New functionality added to Odoo
This change adds a dedicated VAT date to accounting entries, helping businesses record the date used for VAT liability separately from the invoice date. It supports compliance needs in EU countries where VAT is often based on delivery or other legally defined dates.
Original PR description
Description of the issue/feature this PR addresses: Please take consider add new field for vat date. Its comming from VAT liability regulations in countries in EU. In most cases VAT date is defined as date of delivery. Please take a look in file with compare of legislation in countries of EU. You will see expected source of date and also source of legal path for it. https://docs.google.com/spreadsheets/d/1oXS4OXu7lJqiEhfld6vxNbzKPnMP5rS5/edit?usp=sharing&ouid=116659028662340341286&rtpof=true&sd=true This small change will make a big step ahead and simplify a lot in accounting. Thanks for support. Current behavior before PR: No vat_date field in account_move model Desired behavior after PR is merged: New vat_date field in account_move model should be present. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Enhancements to existing features
Tax reports now include options to hide lines that have zero values or no related data. This helps users produce cleaner reports by removing irrelevant rows and making important tax figures easier to review.
Original PR description
…pty' in Tax report Add two options 'Hide if Zero' and 'Hide If Empty' in Tax report, 'Hide If Empty' only works based on 'Target id' same as like in 'Financial Report' 'Hide If Empty' only works based on 'Domain name' opw-2613012 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
Manufacturing order splits now allow a lot or serial number to be assigned to each resulting backorder. The original order also records a note listing the created backorders, improving traceability for production teams.
Original PR description
With this commit ============= - Added a field lot/serial number for backorder & log-note when mo is splited we can give a lot/serial number to each backorder at the time of splitting mo. We have added a lot/serial no field in split wizard too, same as like mo. - After splitting mo I have added a log note in main mo like "This manufacture order is splited to" (splited backorder names) TaskId - 2754217
Features or functions removed from Odoo
The Point of Sale no longer loads products and customers in the background, a feature that could slow down businesses with large catalogs or customer lists. Instead, it loads a fixed amount of data when opening the Point of Sale, improving predictability and reducing performance issues.
Original PR description
In a previous PR, we changed the default value of the background loading of the partners and products to false in 16.0 to saas-16.2 because the features were causing loss of performance in the pos when clients had lot of products or partners. We now remove completly this feature saas-16.3 and hardcode the number of loaded products and partners at the opening of the PoS to respectively 20000 and 100. Upgrade PR: odoo/upgrade#4531 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Miscellaneous changes
Since [this other commit], an error is displayed when the language selector is opened. This commit fixes the issue. Steps to reproduce the issue: - Edit a website page - Click on the navbar - Set the language selector option to 'Dropdown' - Set the header template to Sidebar - Save - Click on the language selector => An error is displayed The error was only present for languages selectors that were in a sidebar because in this case the element that has the dropdown class does not
Original PR description
Since [this other commit], an error is displayed when the language selector is opened. This commit fixes the issue. Steps to reproduce the issue: - Edit a website page - Click on the navbar - Set the language selector option to 'Dropdown' - Set the header template to Sidebar - Save - Click on the language selector => An error is displayed The error was only present for languages selectors that were in a sidebar because in this case the element that has the dropdown class does not have the nav-item class. [this other commit]: https://github.com/odoo/odoo/commit/b6963dc21bad4b012aace16b9ea9264c33a0d618 opw-3247507 Forward-Port-Of: odoo/odoo#118148
The project dependency list has been updated to match versions available in Ubuntu 22.04 while keeping compatibility with Debian Bullseye in mind. This helps deployments on newer Ubuntu systems run with supported package versions and reduces environment mismatch issues.
Original PR description
With the release of the Ubuntu 22.04 Jammy Jellyfish, the time has come for our requirements to make the usual JCVD style big gap between the latest Ubuntu stable and the latest Debian stable 11.4…
With the release of the Ubuntu 22.04 Jammy Jellyfish, the time has come for our requirements to make the usual JCVD style big gap between the latest Ubuntu stable and the latest Debian stable 11.4 Bullseye. | | Debian Bullseye | Ubuntu Jammy | | --------------------|---------------------------|----------------------| | chardet | [4.0.0](https://packages.debian.org/bullseye/python3-chardet) | [4.0.0](https://packages.ubuntu.com/jammy/python3-chardet) | | idna | [2.10](https://packages.debian.org/bullseye/python3-idna) | [3.3](https://packages.ubuntu.com/jammy/python3-idna)| | libsass | [0.20.1](https://packages.debian.org/bullseye/python3-libsass) | [0.20.1](https://packages.ubuntu.com/jammy/python3-libsass)| | Markupsafe | [1.1.1](https://packages.debian.org/bullseye/python3-markupsafe) | [2.0.1](https://packages.ubuntu.com/jammy/python3-markupsafe) | | num2words | [0.5.9](https://packages.debian.org/bullseye/python3-num2words) | [0.5.10](https://packages.ubuntu.com/jammy/python3-num2words)| |passlib| [1.7.4](https://packages.debian.org/bullseye/python3-passlib)|[1.7.4](https://packages.ubuntu.com/jammy/python3-passlib)| |psutil |[5.8.0](https://packages.debian.org/bullseye/python3-psutil)|[5.9.0](https://packages.ubuntu.com/jammy/python3-psutil)| |pydot|[1.4.2](https://packages.debian.org/bullseye/python3-pydot)|[1.4.2](https://packages.ubuntu.com/jammy/python3-pydot)| |pyopenssl|[20.0.1](https://packages.debian.org/bullseye/python3-openssl)|[21.0.0](https://packages.ubuntu.com/jammy/python3-openssl)| |pyserial|[3.5](https://packages.debian.org/bullseye/python3-serial)|[3.5](https://packages.ubuntu.com/jammy/python3-serial)| |python-dateutil|[2.8.1](https://packages.debian.org/bullseye/python3-dateutil)|[2.8.1](https://packages.ubuntu.com/jammy/python3-dateutil)| |stdnum|[1.16](https://packages.debian.org/bullseye/python3-stdnum)|[1.17](https://packages.ubuntu.com/jammy/python3-stdnum)| |pytz|[2021.1](https://packages.debian.org/bullseye/python3-tz)|[2022.1](https://packages.ubuntu.com/jammy/python3-tz)| |zeep|[4.0.0](https://packages.debian.org/bullseye/python3-zeep)|[4.1.0](https://packages.ubuntu.com/jammy/python3-zeep)|
User profile XP changes are now easier to interpret because decreases are shown with an orange warning badge instead of the same green success badge used for increases. This helps users and administrators quickly distinguish positive XP gains from negative XP adjustments.
Original PR description
before this commit, if an user receive an increase or decrease in the XP, both are currently shown with success badge(green). after this commit, if there is decrease in user XP, it will be shown with warning badge(orange) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Point of Sale users can now set a fixed monetary amount for sale order down payments instead of manually calculating a percentage. This makes checkout workflows faster and reduces errors when customers agree to a specific deposit amount.
Original PR description
Until now, it was not possible to apply fixed amount on downpayment. Users were forced to compute the percentage to apply on a downpayment on the side when the wanted to apply a fixed downpayment. This is no more the case thanks to a new setting in the configuration of the configs. task-id: 2836904 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Localization module information now directs users to Odoo’s own documentation instead of external sources. This gives customers and partners a more consistent, reliable source for learning about standard country-specific localization features.
Original PR description
Removing external links from localization manifests and redirect to our own documentation. Ensure that users can learn about our standard localization modules from a source of information that we have authorship on. Task-Id: 3248632 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Odoo can now position popovers correctly when the referenced content is inside an embedded page. This improves guidance and contextual UI elements in screens that use iframes, while keeping a known limitation around scrolling behavior in some cases.
Original PR description
Before this commit: It is not possible to add a popover in an iframe (with the popover service of an app from outside the iframe). After this commit: The position hook now finds out the possible target's iframe element, from which it can compute an offset so it could position properly the popper element. Known limitations: The popover element is not attached inside the iframe's DOM, so there may be some cases where the popover is shown outside of the iframe (depends on scrolling). TaskId: 3184061
Learners who leave an eLearning course are now archived instead of deleted, so their progress, survey answers, and earned karma can be restored if they rejoin. Course managers also get clearer backend visibility with archived filters, next lesson information, and improved course status indicators.
Original PR description
TaskID : 2199207 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Point of Sale now offers a clearer restaurant floor layout, including a mobile-friendly kanban view and easier table and floor management from the front end. The update also streamlines navigation by grouping actions into a menu, helping staff work faster on smaller screens and busy floor plans.
Original PR description
Currently, there is only 1 plan view that is unreadable on mobile and sometimes also complicated in some cases. This commit adds a new "Kanban" view used by default on mobile and available in desktop too. This commit also changes the edit bar of the FloorScreen: the design is changed and some features are added like the multiple selection of the tables or the adding and removing of floors directly from the frontend. It also changes the navbar of the PoS, moving the buttons in a navigation menu accessible thanks to a button. Related Enterprise PR: odoo/enterprise#38699 Task-id: 3212032 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Survey questions with single or multiple choice answers are now treated as scored only when at least one answer is marked correct. This prevents misleading statistics, such as showing incorrect answers for questions that cannot actually be answered correctly.
Original PR description
This commit slightly modifies the condition to be considered as a "scored question" for questions of type simple/multi choice. Now, to be scored, you need to have at least one correct answer. This notably allows not showing "incorrect answer: 1" when displaying survey statistics as there is no way to get it correctly. Task-3224732
The slide lesson page layout now aligns external sources and additional resources more consistently. This improves readability and gives learners a cleaner, more polished experience when viewing slide content.
Original PR description
Make the alignment proper between 'external sources' and 'additional resources' by using the 'col' classes and add the spacing between them. Task-3229139 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update simplifies some internal point of sale code that handles item merging and price calculations. It should make the system easier to maintain while keeping day-to-day behavior unchanged for users.
The wording shown when generating timesheets for time off has been updated to be easier for end users to understand. This helps employees and administrators better interpret the information after recent changes to the time off timesheet flow.
Original PR description
Before this commit generating timesheet for time off doesn't have clearer info after the recent change. This commit update info according to recent changes to have better understanding to end user. task-3186664
Point of Sale hardware-related actions have been moved from the top navigation bar into the new navigation menu. This keeps hardware controls such as IoT and scale actions aligned with the redesigned Point of Sale interface, making the experience more consistent for store staff.
Original PR description
This commit is related to the change made to the navbar of the PoS. The button of the navbar of the PoS are now moved to a navigation menu. All buttons previously present on the navbar must therefor be adapted to a menu. Related Community PR: odoo/odoo#116534
Users can now filter and find documents using related products or product templates. This makes it faster to locate product-specific documents and improves day-to-day document management.
Original PR description
In this commit, We have added product and product template in document search view. so user can easily search documents. task-3146188
Subscription closures can now be recorded with more specific reasons, including cases closed automatically by OdooBot. Key close reasons used in business flows are protected from deletion, helping teams keep reliable data for reporting and analysis.
Original PR description
Currently it is difficult to analyse why subscriptions have been closed because for most of them there is no close reason defined as OdooBot does not provide any information when closing sub. This commit improves the close reasons and implements a boolean field that prevents users from deleting close reasons that are required in business flows. task-3102584
Payroll users now get a dedicated pivot reporting view for payslips instead of a generic automatically generated layout. This makes it easier to analyze payslips in the To Pay reporting area and improves reporting clarity.
Original PR description
before this commit, there is no pivot view defined for the hr.payslip model and on accessing pivot view of this model, currently odoo generated view is showing. * payslips -> Reporting -> To Pay * switch to pivot view after this commit, the pivot view will be added for hr.payslip model
The signing template editor has been modernized to make it easier to maintain and evolve. This update helps reduce reliance on older browser technologies while adding automated checks to protect the template editing experience.
Original PR description
This commit converts the sign.Template client action to OWL. This is the first part of a series of tasks seeking to convert the whole sign module to OWL and stop using jQuery and jQuery-based…
This commit converts the sign.Template client action to OWL. This is the first part of a series of tasks seeking to convert the whole sign module to OWL and stop using jQuery and jQuery-based libraries. Due to some specificities of the sign module, it was not possible to use OWL inside the iframe. This is due to the fact that the content inside the iframe is controlled by PDF.js and, since we need to add DOM our own elements in different pages rendered by a third-party library, using OWL didn't make a lot of sense as it was not possible to mount an OWL application on a single element inside the iframe. Therefore, it was decided to use plain JS to handle the rendering logic inside the iframe. In order to keep the developer experience closer to OWL development, it was decided to use a JS class responsible for rendering our custom elements and handling all interactions with the iframe. This also allows us to extend the behavior of the base class as we want to have different iframe behaviors in the frontend/backend. Even inside the iframe class, it was possible to use renderToString to dynamically render the sign items, so we were still able to use owl templates. Also, it is possible to pass OWL services to the class in the constructor, so we were able to use the rpc, orm, dialog and popover services inside the iframe class. On top of that, a tour was created to test the template edition functionality and guarantee that it isn't broken. task-3071044
The Subscriptions app has been streamlined with clearer renewal views, improved form fields, and better layout behavior. These changes make it easier for users and managers to review pricing, close reasons, subscription counts, and prorated billing details.
Original PR description
In this commit, the following changes were made to improve the UX in the Subscriptions app: - Remove 'Quotation' and 'Closed' section from the 'Subscriptions to Renew' view. - Add 'Pricelist menu' field in the subscriptions form when the pricelist setting is active. - Fix the layout bug which was overlaying the 'number of subscriptions' label with the 'Subscriptions' label. - Add 'Close reason' field in subscriptions form and allow the manager to edit it. - Update the prorata description adding temporal information regarding its recurrence period. Task-id: 3186235
Tax reports now include options to hide lines that are zero or empty, making reports cleaner and easier to review. This helps users focus on relevant tax information and reduces unnecessary clutter in generated reports.
Original PR description
…pty' in Tax report Add two options 'Hide if Zero' and 'Hide If Empty' in Tax report, 'Hide If Empty' only works based on 'tag_name' same as like in 'Financial Report' 'Hide If Empty' only works based on 'Domain name' opw-2613012
The Knowledge article dialog now opens at a medium size instead of a large one. This creates a more balanced layout and avoids unnecessary empty space when users open articles.
Original PR description
**Purpose:** When user opens the article dialog box(from '/Article'), it opens with a large size and there is no point of having it this long. **Specification:** Reduce the size of the dialog box to medium for an appropriate look. **Task**-3252594
Users now see a visual indication when they try to drag and drop files into the Documents “All” workspace, where dropping is not allowed. This helps prevent confusion by making the restriction visible at the moment of action.
Original PR description
This commit adds a visual effect when one is trying to drag and drop a file in the "all" workspace which is forbidden. Task-3225053
This fix prevents an error from appearing when someone clicks an empty user avatar field. It improves stability in the Mail-related user interface and avoids interrupting users with a traceback.
Original PR description
m2o avater user widget This commit's purpose is to prevent a traceback when the user click on an empty avatar user icon. task-3254564 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
Replace matched filter by unmatched in payment view. It makes more sense to find payments that are unmatched. task-id: 3231191 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#117055
Original PR description
Replace matched filter by unmatched in payment view. It makes more sense to find payments that are unmatched. task-id: 3231191 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#117055
Steps to reproduce: - set early_pay_discount_computation on company to mixed. - create an expense with taxes - try to post entries from the expense > traceback This commit adds the missing key in the needed_terms computed on in hr_expense. We could have bypassed the computation in the case of expenses but simply adding the key sounds like a more future-proof solution. opw-3244294 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Por
Original PR description
Steps to reproduce: - set early_pay_discount_computation on company to mixed. - create an expense with taxes - try to post entries from the expense > traceback This commit adds the missing key in the needed_terms computed on in hr_expense. We could have bypassed the computation in the case of expenses but simply adding the key sounds like a more future-proof solution. opw-3244294 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#117139
"Order by" makes the query really slow. On a database with 1000000 partner and 10000 user, this query goes from 5.5s to 600ms. Once cached by Pgsql it goes down below 100ms. task-2982401 Forward-Port-Of: odoo/odoo#118217
Original PR description
"Order by" makes the query really slow. On a database with 1000000 partner and 10000 user, this query goes from 5.5s to 600ms. Once cached by Pgsql it goes down below 100ms. task-2982401 Forward-Port-Of: odoo/odoo#118217
task - 3062158 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#118072 Forward-Port-Of: odoo/odoo#114689
Original PR description
task - 3062158 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#118072 Forward-Port-Of: odoo/odoo#114689
Tracked binary fields do not produce any message in the chatter Steps to reproduce: 1. Install Sales and Studio 2. Open any quotation 3. Trigger Studio and add a signature field to the form 4. With debug mode enabled, edit the field (by clicking on MORE when the field is selected) and set the Enable Ordered Tracking to 1 5. Close Studio 6. Edit the signature and save 7. No message appears in the chatter to track the value Solution: Remove the `tracking` field from binary fields to
Original PR description
Tracked binary fields do not produce any message in the chatter Steps to reproduce: 1. Install Sales and Studio 2. Open any quotation 3. Trigger Studio and add a signature field to the form 4. With debug mode enabled, edit the field (by clicking on MORE when the field is selected) and set the Enable Ordered Tracking to 1 5. Close Studio 6. Edit the signature and save 7. No message appears in the chatter to track the value Solution: Remove the `tracking` field from binary fields to prevent the user from trying to track it Problem: We shouldn't track binary data in the chatter and we cannot use the filenames opw-3055108 task-3255810 Forward-Port-Of: odoo/odoo#118243 Forward-Port-Of: odoo/odoo#117821
**Steps to reproduce:** 1. Go to Manufacturing App 2. Click on some MO 3. When pressing the 'ALT' shortcut key the Scrap and Cancel tabs offer the letter 'Z'. According to [this spreadsheet ](https://docs.google.com/spreadsheets/d/1QIPwUiEDv37H1P_FjN-WctzPey2Niu6K5dCL157Z8BY/edit#gid=0) the scrap action (line 79) should be assigned to shortkey 'Y' OPW-3202893 Forward-Port-Of: odoo/odoo#117563 Forward-Port-Of: odoo/odoo#117112
Original PR description
**Steps to reproduce:** 1. Go to Manufacturing App 2. Click on some MO 3. When pressing the 'ALT' shortcut key the Scrap and Cancel tabs offer the letter 'Z'. According to [this spreadsheet ](https://docs.google.com/spreadsheets/d/1QIPwUiEDv37H1P_FjN-WctzPey2Niu6K5dCL157Z8BY/edit#gid=0) the scrap action (line 79) should be assigned to shortkey 'Y' OPW-3202893 Forward-Port-Of: odoo/odoo#117563 Forward-Port-Of: odoo/odoo#117112
This PR fixes the following issues, and adds the related missing unit tests. **Before this PR:** 1. Pasting an image or video URL as simple text was failing, and pasting it as a link was undoing the last modification before it. 2. Pasting image/video URL + other text fragments: The powerbox commands are not compatible with pasting text containing: - one image/video URL and other text fragments - multiple URLs. Choosing
Original PR description
This PR fixes the following issues, and adds the related missing unit tests. **Before this PR:** 1. Pasting an image or video URL as simple text was failing, and pasting it as a link was undoing the…
This PR fixes the following issues, and adds the related missing unit tests.
**Before this PR:**
1. Pasting an image or video URL as simple text was failing, and pasting it as a link was undoing the last modification before it.
2. Pasting image/video URL + other text fragments: The powerbox commands are not compatible with pasting text containing:
- one image/video URL and other text fragments
- multiple URLs.
Choosing to embed the image/video or to paste it as URL leads to loss of all text fragments and URLs but the last URL.
3. Pasting image URL inside an existing link: Even though the Editor's specs do not allow a URL to be transformed into a link when pasting it inside an existing link, pasting an image URL inside a link opens the powerbox with 3 commands, one of them allowing to transform the URL into a link.
~4. When pasting an image URL inside an "isolated" link (after having clicked on it and making it the only contenteditable in the document), the cursor disappeared, preventing the powerbox to open (it would open later when insering text somewhere outside the link).~
5. The Selection is not properly restored when UNDOing after pasting over a non-collapsed selection:
- a valid URL (not image or video)
- text composed of a valid URL between text fragments
6. When pasting media URL the powerbox would open with 2 command groups, containing one command each. Grouping is useless in this case.
7. Pasting media URL with the mouse (right click + paste) failed to open Powerbox
8. Pasting content inside an (invisible) empty link or when all its inner contents were selected lead to undesired effects, among which having nested links (see [task-3081254](https://www.odoo.com/web#id=3081254&menu_id=4720&cids=1&action=333&active_id=1695&model=project.task&view_type=form))
**After this PR:**
1. Image and video URLs can be pasted as a link ~or as text~.
~But another issue arises from being able to paste a URL as text: if the user wishes to type further after the URL, hitting the SPACE key transforms the recently pasted URL behind the cursor. In order to prevent this, this PR proposes the following spec:~
~When pasting a URL as text at the end of a line, an extra space is added.~
~Otherwise the user would have no way to type more text in that line without transforming the URL into a link.
Pasting the URL somewhere other than right before a line break does not lead to the addition of an extra space, as this would mostly likely lead to an undesired inclusion of a space.~
Pasting a URL as plain text is no longer possible, as this was considered a useless command.
2. The powerbox does not open when pasting multiple URLs or URL + other text fragments.
This does not change current spec, in which related tests only dealt with the scenario of pasting a single image/video URL. It proposes only that the current spec should not apply to the cases other than a single URL. In such cases, normal pasting with URL transformation takes place.
3. The powerbox no longer opens when pasting a image URL inside a link, and the image is embedded directly. The logic for selecting the suitable powerbox commands when pasting URL was rewritten.
~4. The cursor position is restored after pasting an image URL inside an isolated link, and the powerbox opens.~
5. Selection is properly restored after paste + UNDO.
6. Command groups were removed from powerbox upon paste of media URL.
7. Pasting media URL with the mouse opens Powerbox as expected.
8. In order to prevent inadvertently pasting content inside a link rather than replacing it, this PR removes the link when pasting content inside an empty link or when all of its text content is selected, letting the pasted content replace it.
**Other minor fixes:**
Unnecessary regex matchings were removed.
Removed argument from call to `historyPauseSteps`, as this function takes no arguments.
See commit messages for details on the technicals.
task-3099012
task-3081254
Forward-Port-Of: odoo/odoo#117246
Forward-Port-Of: odoo/odoo#108755Before this commit, when using chatbot on an external website, the answers were not styled like buttons. This happens because styling is using bootstrap classnames, which are not available in the external lib. This commit fixes the issue by putting SCSS equivalent style rules, so that the answers are properly styled. opw-3234872 Before/After    Forward-Port-Of: odoo/odoo#118209
Commit odoo/enterprise@4bbf70f was fixing a timezone issue. Datetimes coming from lists inserted in a spreadsheet were always displayed in UTC. However, this commit also changed the formatting behavior. Before the fix: date/datetimes were dispalyed with the server format After: they are displayed with the local format (FR if the user lang is French) This can lead to issues because spreadsheet only understands a handfull of date(time) format. For example, it doesn't understand dd/mm/yyyy f
Original PR description
Commit odoo/enterprise@4bbf70f was fixing a timezone issue. Datetimes coming from lists inserted in a spreadsheet were always displayed in UTC. However, this commit also changed the formatting…
Commit odoo/enterprise@4bbf70f was fixing a timezone issue. Datetimes coming from lists inserted in a spreadsheet were always displayed in UTC. However, this commit also changed the formatting behavior. Before the fix: date/datetimes were dispalyed with the server format After: they are displayed with the local format (FR if the user lang is French) This can lead to issues because spreadsheet only understands a handfull of date(time) format. For example, it doesn't understand dd/mm/yyyy format but only the other way around (mm/dd/yyyy) This commit restores the previous format (server format), while preserving the timezone conversion. opw-3251586 Manual forward-port of odoo/enterprise#39438 X-original-commit: odoo/enterprise@c66f8622a5bc09d8ad25ce0850dfb536ebe1b201 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 Forward-Port-Of: odoo/odoo#118207
This pull request does not introduce any product or workflow changes. It was kept empty because a related implementation no longer requires an internal query-count update, so there is no expected impact for users.
Original PR description
Empty PR. This PR was necessary to update the query count with a previous implementation. But with the new implementation, the query count must not be updated so it is now empty. See odoo/enterprise#39449 Task-3082297
If applied, this commit will solve the issue of the archived pos config issue while session accessed from another tab, another device, or another user. Steps to produce: - Open the pos session. - From another device or another tab archive the pos.config record. - Refresh the opened session. sentry - 4057306284 see - https://tinyurl.com/2opdugz4 Forward-Port-Of: odoo/odoo#117584
Original PR description
If applied, this commit will solve the issue of the archived pos config issue while session accessed from another tab, another device, or another user. Steps to produce: - Open the pos session. - From another device or another tab archive the pos.config record. - Refresh the opened session. sentry - 4057306284 see - https://tinyurl.com/2opdugz4 Forward-Port-Of: odoo/odoo#117584
Issue: CSRF token was being cached and this caused issues when the session id was updated. Post requests would continue to use the old CSRF token and it would not be able to be validated with the session id. Solution: Added the t-nocache attribute to every instance where csrf_token is called in the case that the session_id is different. This is changed to behave the same as the csrf token input in the products_item template. opw-3256880 --- I confirm I have signed the CLA and read th
Original PR description
Issue: CSRF token was being cached and this caused issues when the session id was updated. Post requests would continue to use the old CSRF token and it would not be able to be validated with the session id. Solution: Added the t-nocache attribute to every instance where csrf_token is called in the case that the session_id is different. This is changed to behave the same as the csrf token input in the products_item template. opw-3256880 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#117861
[FIX] mass_mailing,mail: fullwidth chatter & spacing The Email Marketing app being in full width with a different chatter behavior, its template was clashing with the inner navigation. Moreover some inputs and labels had weird spacing and uneven responsive behavior. This commit removes the borders from the chatter `.o_ChatterTopbar_tool` and next to the activity btn. However, since the inner chatter template is inaccessible through `<xpath>` and the borders were applied with bs c
Original PR description
[FIX] mass_mailing,mail: fullwidth chatter & spacing The Email Marketing app being in full width with a different chatter behavior, its template was clashing with the inner navigation. Moreover some…
[FIX] mass_mailing,mail: fullwidth chatter & spacing The Email Marketing app being in full width with a different chatter behavior, its template was clashing with the inner navigation. Moreover some inputs and labels had weird spacing and uneven responsive behavior. This commit removes the borders from the chatter `.o_ChatterTopbar_tool` and next to the activity btn. However, since the inner chatter template is inaccessible through `<xpath>` and the borders were applied with bs classes, this required the use of CSS variable to avoid an ugly overrides on the border property with an `!important`. This use of CSS variable allows to display borders by default except when the variable is defined inside the `mass_mailing.scss` which removes the borders for this specific use case. To allow better control and not alter the current behavior a new class has been added: `o_ChatterTopbar_borderLeft`. To even the spacing between the nav, the chatter's topbar and the chatter messages, a negative margin is applied on first child of `o_MessageList_separator` for mass_mailing. This allows the override of the `pt-4`. Moreover, in community if the chatter is in full width, the box-shadow of the `Send message` btn was cut on the left side by the `overflow: auto` on the .o_ChatterContainer, to avoid this behavior the same CSS variable logic is used, using the `--ChatterContainer-overflow` in the file `chatter_containers.scss` with a default value of `auto` and `visible` when the variable is defined (in mass_mailing). The same logic is used in `activity_box.xml, .scss` with the variable `--ActivityBox_title-margin` to override the existing margin-top. To fix the spacing issue this commits changes the padding top on the Select mailing list `label` to be applied only in `sm` screens. For small screens in mass_mailing, the default padding-left next to the Send message is set to 0 with the variable `--ChatterTopbar-padding-left` Finally to avoid the `o_domain_selector` component's huge size on lg screen, the class `w-lg-50` has been added. task-3109579 [Before fix]   [After fix]  --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#117418 Forward-Port-Of: odoo/odoo#110145
- Inactivate unused identification types: passport and unknown - Fix website in the manifest to point to official documentation - Fix data in some taxes - Adds reimbursement taxes --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#113581
Original PR description
- Inactivate unused identification types: passport and unknown - Fix website in the manifest to point to official documentation - Fix data in some taxes - Adds reimbursement taxes --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#113581
[FIX] decimal position in unit test sample EDI XML files, using 2 decimal places instead of 6, not because it gave errors but because the technical specification states 6 decimal places solely for the fields unit_price and product_quantity and also because it is just impossible to have 6 decimal places in a country with USD as currency (In USD it is impossible to have a coin smaller than 0.01). [FIX] A few translations [FIX] Validation for requiring the payment method on sale invoice and purch
Original PR description
[FIX] decimal position in unit test sample EDI XML files, using 2 decimal places instead of 6, not because it gave errors but because the technical specification states 6 decimal places solely for…
[FIX] decimal position in unit test sample EDI XML files, using 2 decimal places instead of 6, not because it gave errors but because the technical specification states 6 decimal places solely for the fields unit_price and product_quantity and also because it is just impossible to have 6 decimal places in a country with USD as currency (In USD it is impossible to have a coin smaller than 0.01). [FIX] A few translations [FIX] Validation for requiring the payment method on sale invoice and purchase liquidation only [FIX] Fix typos in a few tax templates [FIX] Improves withhold report with better vertical alignment for the tax support and a few lines to make it more transparent which withhold taxes belong to which tax supports (we vertically center the tax support in the middle of its withhold taxes) [FIX] Payment method in tests, to use a payment method that is in use nowadays (replaces code 17 electronic money with code 01 other methods, electronic money is no longer existent in Ecuador) [FIX] Foreign supplier withhold test, by setting the proper tax regime (a foreign one) and using a foreign withhold tax. (It didn't break the tests before because the foreign regime is required in the view and not in python) [ADD] Adds reimbursement taxes which were missing Forward-Port-Of: odoo/enterprise#37505
steps: helpdesk > configuration > teams > create a team cause: while creating a team the default color was set on it issue: default color was set on the teams fix: change the default color of the team to none task-3141892 Forward-Port-Of: odoo/enterprise#39546 Forward-Port-Of: odoo/enterprise#36042
Original PR description
steps: helpdesk > configuration > teams > create a team cause: while creating a team the default color was set on it issue: default color was set on the teams fix: change the default color of the team to none task-3141892 Forward-Port-Of: odoo/enterprise#39546 Forward-Port-Of: odoo/enterprise#36042
At the moment, the input for external value (manual input) is not centered. It's aligned at the top and doesn't look nice next to the "Post" button. This commit aligns the input at the center. Forward-Port-Of: odoo/enterprise#39463
Original PR description
At the moment, the input for external value (manual input) is not centered. It's aligned at the top and doesn't look nice next to the "Post" button. This commit aligns the input at the center. Forward-Port-Of: odoo/enterprise#39463
### Bug Currently, trying to export (PDF or XLSX) any consolidation balance will always export the latest one (the one with larges `id`). ### Steps to reproduce 1. create multiple consolidations 2. go to any consolidation balance 3. click on`PDF` or `XLSX` to export the report You should see that no matter which consolidation you try to export, you always get the same file. opw-3229643 Forward-Port-Of: odoo/enterprise#39221
Original PR description
### Bug Currently, trying to export (PDF or XLSX) any consolidation balance will always export the latest one (the one with larges `id`). ### Steps to reproduce 1. create multiple consolidations 2. go to any consolidation balance 3. click on`PDF` or `XLSX` to export the report You should see that no matter which consolidation you try to export, you always get the same file. opw-3229643 Forward-Port-Of: odoo/enterprise#39221
task - 3062158 Forward-Port-Of: odoo/enterprise#39516 Forward-Port-Of: odoo/enterprise#37917
Original PR description
task - 3062158 Forward-Port-Of: odoo/enterprise#39516 Forward-Port-Of: odoo/enterprise#37917
Right now the signature request smartbutton only displays sign requests sent to work emails, but an employee might not have a work email set yet when using the recruitment app for example. So the behavior after this PR is : take work email if it exists, if not take the private email, if no email is set notify the user. task - 3240123 Forward-Port-Of: odoo/enterprise#39382 Forward-Port-Of: odoo/enterprise#38535
Original PR description
Right now the signature request smartbutton only displays sign requests sent to work emails, but an employee might not have a work email set yet when using the recruitment app for example. So the behavior after this PR is : take work email if it exists, if not take the private email, if no email is set notify the user. task - 3240123 Forward-Port-Of: odoo/enterprise#39382 Forward-Port-Of: odoo/enterprise#38535