Thursday, January 28, 2021
31 changes · master
New functionality added to Odoo
The community documentation now includes guidance for the grid view that was previously only available in the enterprise documentation. This makes it easier for users and implementers to understand grid view options and recent related attributes in one shared documentation source.
Original PR description
task-2271628 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Enhancements to existing features
Graph charts now use the custom label defined in the view for measure fields, instead of always falling back to the generic field name. This keeps chart labels, popovers, and measure dropdowns consistent, reducing confusion for users reading reports.
Original PR description
PURPOSE The graph view fields can have the "string" attribute. Unfortunately, it is not used by in the chart.js instance to update the labels and popover. SPEC When we define a graph view, the string attribute is ignored in the label and popover, use field strings given in view definition on more priority then field definition. TASK 2264636 -- 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 fixes the displayed label for the Warehouse field in Point of Sale settings. It helps users see the correct wording in the configuration screen, reducing confusion when setting up sales locations.
Original PR description
Use correct field label for Warehouse Followup on dd2aaf0b1dc4ff3997ca753ee1feb67920f5cbfa 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
Documentation and clarification updates
This update adds a new email address to the corporate contributor license agreement record for i3 Rendszerház Kft. It helps keep Odoo's contributor legal documentation accurate and up to date.
Original PR description
Add my name i3 Rendszerház Kft. 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
Miscellaneous changes
Behavior prior to this commit: When a PO is generated (via reordering rule, mto rule, or manual replenish), the description on the PO line includes the internal notes. Behavior after this commit: The description on the PO line does not include the internal notes. opw-24222438 (partial) Forward-Port-Of: odoo/odoo#63892
Original PR description
Behavior prior to this commit: When a PO is generated (via reordering rule, mto rule, or manual replenish), the description on the PO line includes the internal notes. Behavior after this commit: The description on the PO line does not include the internal notes. opw-24222438 (partial) Forward-Port-Of: odoo/odoo#63892
Users now receive a logged confirmation or error message when testing mass emails or SMS campaigns, making it clear whether the test worked and why it may have failed. Email and phone test inputs are also easier to validate by separating entries line by line.
Original PR description
…gs/sms This commit adds user feedback in the form of a message logged on the related document (mailing.mailing) when testing a mailing/sms. Before this change, when sending an email to your own mailbox for testing purpose, or when sending an SMS to your phone, you did not get any interface feedback on whether it worked or not. Now, a logged message will show if it's successful and if not, explain why it failed with a short error message (no IAP credits / misconfigured outgoing mail server / ...). Task 2375526 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
Employees can now set their preferred language directly from their employee profile or personal profile instead of relying on the private address record. This makes profile management easier and helps ensure employee-facing content appears in the right language.
Original PR description
The field is defined on the private address (address_home_id) of the employee. It would be more convenient to allow the configuration directly on the employee view and to allow the employee to change it by himself. TaskID: 2410407 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
Mobile users can now add calendar events with a simple tap, while the existing long-tap option remains available. Tapping an empty area in month or year views now opens the selected day view, making calendar scheduling faster and more intuitive on mobile devices.
Original PR description
Before this commit, the only way to add an event was using a long tap. After this commit, a short tap will be added. So to summarize on Mobile there is two methods to add an event using the calendar: short tap and long tap. For month/year views when a user tap on a "Free Zone" (no event) the view is changed in the "day view" for this clicked day. Task ID: 1891957
This update separates workers into Employee, Student, and Contractor categories so contract expectations can be managed more accurately. Employee records and contract history now reflect whether a person is expected to have an employment contract, helping HR teams distinguish regular employees from non-contract worker types.
Original PR description
Prior to this commit: * All employees were treated the same way regarding the contractual point of vue. From this commit on: * Three employee types will be created: - Employee, which is supposed to be under contract - Student & Contractor which are both not supposed to have an employee contract (but are still use the employee as working for the company) * Employee view and Contract History will take this consideration into account. 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
Employees in Belgium can now select the language used for their payroll-related salary package documents. This improves clarity for employees and helps companies provide localized HR communication more easily.
Original PR description
…oll lang
The Timesheets grid now places the Add a line action directly inside the grid, avoiding conflicts with the timer header and making entry more consistent with grouped lists. Empty timesheet periods can also keep showing the grid and date headers, so users stay oriented even when no records exist.
Original PR description
### Purpose: - The current 'Add a line' button in Timesheets is conflicting with the timer header. The idea is to replace the main 'add a line' button with a button in the grid view itself, so we would have something similar to the grouped list view. This would be possible through the use of a new attribute on the grid. - The help arch from the help field of the 'ir.actions.act_window' was displayed when not record were available (default odoo behavior). Because of that, the user was loosing track of the period he was in. The idea is to add an attribute on the grid that allow to keep the grid visible even when it does not contain any data. task-2271628 Related PR: odoo/odoo#65081
Mobile calendar users can now add events with a simple tap, instead of relying only on a long press. This makes event creation faster and more intuitive, while month and year views still open the selected day when tapping an empty area.
Original PR description
Before this commit, the only way to add an event was using a long tap.
After this commit, a short tap will be added.
So to summarize on Mobile there is two methods to add an event using the
calendar:
* long tap: this open usually the QuickCreate modal with the start and
the end predefined
* short tap: this will redirect to the full Create Event form with only
the start predefined
For month/year views when a user tap on a "Free Zone" (no event)
the view is changed in the "day view" for this clicked day.
Task ID: 1891957Fixed an issue in Planning where saving an employee shift as a template could still create and show the shift even after the user clicked discard. Users can now mark a shift for template creation directly in the form, so discarded changes no longer leave unwanted shifts in the schedule.
Original PR description
**Before this commit:** In planning module, when user save employee's shift as template by clicking "Save as template" button at that time the shift is created. Then click on discard didn't prevent that shift and display it on gantt view. **After this commit:** Shift will not be displayed after clicking on 'discard'. Instead of using button (Save as template) adding Boolean field 'template_creation' below 'repeat' field for saving shift as template. **LINKS** Task-2322036
Manual timesheet entry now works better for users whose keyboard requires Shift to type a colon in HH:MM time formats. Grid cells also keep the newly typed value visible while updates are being processed, reducing confusing flicker or temporary value changes.
Original PR description
What are the steps to reproduce your issue ? 1. Install 'timesheet_grid' 2. Try to enter a timesheet with keyboard in the format HH:MM What is currently happening ? With some keyboard layouts shift…
What are the steps to reproduce your issue ?
1. Install 'timesheet_grid'
2. Try to enter a timesheet with keyboard in the format HH:MM
What is currently happening ?
With some keyboard layouts shift button must be used to print ":",
but in timesheet there is already a shortcut with Shift which prevents
to set timesheet properly
What are you expecting to happen ?
When typing, press shift without selecting the whole cell
How to fix the bug ?
Don't trigger the Shift event if renderer is in edit mode.
See : opw-2411236
task-2389731
[IMP] web_grid: renderer in editmode while updating grid
This commit aims to keep the input value while the grid renderer is updating grid data's between grid adjustment and grid read_group.
Previous behaviour :
The previous value of the update cell is shown the time between the two rpc calls (adjust_grid, read_group) because the rendering is done just
after adjust_grid with editMode not set and the cell value not updated in the model rendered.
- User triggers _onUpdateValue by writing a new value (let's say : (new : 42, old : 0))
- The rendering is updated during the call to rpc in the grid_controller.js _adjust method.
-> As the state.editMode to render the web_grid.CellValue, the rendering is a div with the cell.value user, which is the previous state value : 0.
- The rendering is updated once again after the result of read_group => Cell value = new_value : 42.
Expected Behaviour :
Between the two rpc calls, the editMode is still true, which allows the web_grid.CellValue template to render an input cell with the currentInput value : 42.
The user get not troubled by the value changes and the behaviour is more smooth regarding UX.
Task-2389731Generate a coupon code, print it opw-2444242 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#64961
Original PR description
Generate a coupon code, print it opw-2444242 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#64961
…ght model This is not really a big issue but let us have correctly defined rules. Spotted during Task ID-2300230 Forward-Port-Of: odoo/odoo#65147
Original PR description
…ght model This is not really a big issue but let us have correctly defined rules. Spotted during Task ID-2300230 Forward-Port-Of: odoo/odoo#65147
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#61998
Original PR description
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#61998
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#64912 Forward-Port-Of: odoo/odoo#64362
Original PR description
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#64912 Forward-Port-Of: odoo/odoo#64362
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#65157 Forward-Port-Of: odoo/odoo#65101
Original PR description
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#65157 Forward-Port-Of: odoo/odoo#65101
Steps to reproduce the bug: - Go to Accounting (module)> Accounting (menu) > Journal Entries - Create a new account move M - Remove the default journal Bug: Impossible to set a journal opw:2445553 Forward-Port-Of: odoo/odoo#65144
Original PR description
Steps to reproduce the bug: - Go to Accounting (module)> Accounting (menu) > Journal Entries - Create a new account move M - Remove the default journal Bug: Impossible to set a journal opw:2445553 Forward-Port-Of: odoo/odoo#65144
…ut currency Follow-up of 13a4544707053295565c33580526f6a8a16f556b Where we fixed the portal *list* of opportunities but did not notice that the associated *form* also had the same issue. To recap the issue: When you remove the 'company_id' on a crm.lead, you also remove the computed 'company_currency'. When trying to view this kind of leads in the website_crm_partner_assign portal form page, it would raise an error while trying to display the planned_revenue in the missing curr
Original PR description
…ut currency Follow-up of 13a4544707053295565c33580526f6a8a16f556b Where we fixed the portal *list* of opportunities but did not notice that the associated *form* also had the same issue. To recap…
…ut currency Follow-up of 13a4544707053295565c33580526f6a8a16f556b Where we fixed the portal *list* of opportunities but did not notice that the associated *form* also had the same issue. To recap the issue: When you remove the 'company_id' on a crm.lead, you also remove the computed 'company_currency'. When trying to view this kind of leads in the website_crm_partner_assign portal form page, it would raise an error while trying to display the planned_revenue in the missing currency. Now, we display the number without any currency sign, which is a "best effort" solution, just the same as on the crm.lead form view. So it will look like "9000 at 47%" instead of "$9000 at 47%". Task-2444539 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#65141 Forward-Port-Of: odoo/odoo#64933
When Odoo is started in worker mode with Python 3.8.5, and gevent/greenlet installed from requirements, the following error message is thrown: `RuntimeWarning: greenlet.greenlet size changed, may indicate binary incompatibility` As a gevent developper stated [1] that gevent 1.5 is not compatible with Python 3.8, this commit bumps the version to 20.9.0 (current version for the next Debian and Ubuntu releases [2] [3]) This commit should not impact those who use the Debian/Ubuntu pack
Original PR description
When Odoo is started in worker mode with Python 3.8.5, and gevent/greenlet installed from requirements, the following error message is thrown: `RuntimeWarning: greenlet.greenlet size changed, may…
When Odoo is started in worker mode with Python 3.8.5, and gevent/greenlet installed from requirements, the following error message is thrown: `RuntimeWarning: greenlet.greenlet size changed, may indicate binary incompatibility` As a gevent developper stated [1] that gevent 1.5 is not compatible with Python 3.8, this commit bumps the version to 20.9.0 (current version for the next Debian and Ubuntu releases [2] [3]) This commit should not impact those who use the Debian/Ubuntu packages of gevent and greenlet. The error does not appear with those versions. In Ubuntu Focal, the packaged version is 1.4.0 [4] but the problem was not reported with this version and python 3.8. For reference, it was bumped to 1.5.0 for Python 3.7 in [5]. And greenlet was bumped too for issues with Python 3.8 and 3.9 in [6]. As a result, the requirements for greenlet/gevents gains even more complexity and should be cleaned when python 3.6 support will be dropped. [1] https://github.com/gevent/gevent/issues/1260 [2] https://packages.debian.org/bullseye/python3-gevent [3] https://packages.ubuntu.com/hirsute/python3-gevent [4] https://packages.ubuntu.com/focal/python3-gevent [5] odoo/odoo@bb0b32bd1a3fc0c047d0787b10e8c1c8d696daa5 [6] odoo/odoo@648635deca67df09417ae55c6eb181c98524b74d Fixes #64106 Forward-Port-Of: odoo/odoo#65012
Issue - Install "Contacts" and "Studio" modules - Go to "Contacts" and switch to Studio - Go to "Reports" tab - Create a new report - Select "External" layout Header and footer are missing on report. Cause Header is displayed if 'company' has a value. However, here, we only check if 'company_id' is available in current record fields, not checking if also set. Solution Check that 'company_id' is set on current record, else, fallback on 'res_company'. opw-244
Original PR description
Issue - Install "Contacts" and "Studio" modules - Go to "Contacts" and switch to Studio - Go to "Reports" tab - Create a new report - Select "External" layout Header and footer are missing on report. Cause Header is displayed if 'company' has a value. However, here, we only check if 'company_id' is available in current record fields, not checking if also set. Solution Check that 'company_id' is set on current record, else, fallback on 'res_company'. opw-2443234 Forward-Port-Of: odoo/odoo#65140
Currently, Chrome show a scrollbar when the placeholder is multilined. Overflow hidden will avoid the scrollbar and we place a nowrap on the placeholder text to avoid the multiline. task-2416058 Forward-Port-Of: odoo/odoo#63984
Original PR description
Currently, Chrome show a scrollbar when the placeholder is multilined. Overflow hidden will avoid the scrollbar and we place a nowrap on the placeholder text to avoid the multiline. task-2416058 Forward-Port-Of: odoo/odoo#63984
By making this tree non-editable, clicking on the rows opens the corresponding form, and gives access to more information and better navigation. Forward-Port-Of: odoo/odoo#65206
Original PR description
By making this tree non-editable, clicking on the rows opens the corresponding form, and gives access to more information and better navigation. Forward-Port-Of: odoo/odoo#65206
Office Outlook doesn't take into account the [style] attribute, and it doesn't manage width/height in percent value. This commit set width/heigth attribute in pixels and also always set the width/height in style attribute (keeping them in the original unit and setting them to auto if not present). This is a reintroduction of 2015 commit bdf58adb465b opw-2447756 Forward-Port-Of: odoo/odoo#65150
Original PR description
Office Outlook doesn't take into account the [style] attribute, and it doesn't manage width/height in percent value. This commit set width/heigth attribute in pixels and also always set the width/height in style attribute (keeping them in the original unit and setting them to auto if not present). This is a reintroduction of 2015 commit bdf58adb465b opw-2447756 Forward-Port-Of: odoo/odoo#65150
Create a product with variants attributes that NEVER create variants. Configure Variants to add some extra-prices to some variants. In POS settings activate "Product Configurator" and "Advanced Pricelists", add the public pricelist and one that applies 5% to the product. Open a session and select the product created (say price = 1$) Select the attributes, the extra-price is added to the product (say the total price now is 2$). Change pricelist from public to 5% and the order line will
Original PR description
Create a product with variants attributes that NEVER create variants. Configure Variants to add some extra-prices to some variants. In POS settings activate "Product Configurator" and "Advanced Pricelists", add the public pricelist and one that applies 5% to the product. Open a session and select the product created (say price = 1$) Select the attributes, the extra-price is added to the product (say the total price now is 2$). Change pricelist from public to 5% and the order line will show our product = 0.95, not taking the extra-prices into account (so not 1.9, i.e. 5% of the 2$ that were formerly displayed) opw-2439445 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#64861
Before this commit, dropzones were created around invisible elements (e.g. the snippet popup). So we had 2 dropzones instead of one at some locations. After this commit, we avoid creating dropzones around elements that must not have dropzones. task-2312878 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-P
Original PR description
Before this commit, dropzones were created around invisible elements (e.g. the snippet popup). So we had 2 dropzones instead of one at some locations. After this commit, we avoid creating dropzones around elements that must not have dropzones. task-2312878 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#65198
Before this commit, when the purchase order was automatically confirm and send to the partner, the pdf send was the one of the request for quotation. Now, the pdf send is the purchase order. opw-2427046 Forward-Port-Of: odoo/enterprise#15995
Original PR description
Before this commit, when the purchase order was automatically confirm and send to the partner, the pdf send was the one of the request for quotation. Now, the pdf send is the purchase order. opw-2427046 Forward-Port-Of: odoo/enterprise#15995
Allows export of electronic reports in Luxembourg's XML 2.0 format, according to the ecdf rules (cfr. https://ecdf-developer.b2g.etat.lu/ecdf/home). Odoo's interface has been validated by ecdf using this module. Supported reports: * Annual accounts: P&L + Balance Sheet + CoA * VAT declarations: monthly + quarterly + yearly + yearly simplified declarations * VAT IC recapitulative statements: {goods, services} x {monthly, quarterly} + appendix "Tables of acquisitions/amortisable expendit
Original PR description
Allows export of electronic reports in Luxembourg's XML 2.0 format, according to the ecdf rules (cfr. https://ecdf-developer.b2g.etat.lu/ecdf/home).
Odoo's interface has been validated by ecdf using this module.
Supported reports:
* Annual accounts: P&L + Balance Sheet + CoA
* VAT declarations: monthly + quarterly + yearly + yearly simplified declarations
* VAT IC recapitulative statements: {goods, services} x {monthly, quarterly} + appendix "Tables of acquisitions/amortisable expenditures"
Forward-Port-Of: odoo/enterprise#15916
Forward-Port-Of: odoo/enterprise#15460When checking the revenue KPIs, the net revenue is always 0. To reproduce the error: 1. Go to sales, create a SO - Product must be a subscription product 2. Confirm, Create Invoice 3. Post the invoice, Register the payment 4. Go to Subscriptions - You find the subscription you just created in the In-Progress column 5. Reporting > Revenue KPIs 6. Set the date range so your subscription will be included, Update Error: All charts but the Net Revenue are updated. The Net Revenue is
Original PR description
When checking the revenue KPIs, the net revenue is always 0. To reproduce the error: 1. Go to sales, create a SO - Product must be a subscription product 2. Confirm, Create Invoice 3. Post the invoice, Register the payment 4. Go to Subscriptions - You find the subscription you just created in the In-Progress column 5. Reporting > Revenue KPIs 6. Set the date range so your subscription will be included, Update Error: All charts but the Net Revenue are updated. The Net Revenue is still $0. It should at least include the sold and paid subscription (from steps 1-3). The error comes from the SQL request conditions used to compute the net revenue. The SQL result includes the reconciliation lines, therefore the sum is 0. OPW-2431880 Forward-Port-Of: odoo/enterprise#15906