- Nov 12, 2019
-
-
Victor Feyens authored
When assigning a default value to a computed monetary field, if self contains records with different currencies, the assignation will fail when trying to round the value (because self[currency_field] is a recordset of multiple currencies). Globally, assigning a monetary value to records in different currencies should never happen. The only case we want to support is defaulting a computed monetary to 0.0. Add clear error when trying to set monetaries in multi-currency. closes odoo/odoo#40155 X-original-commit: 3a58dfa1 Signed-off-by:
Victor Feyens (vfe) <vfe@odoo.com> Co-authored-by:
Raphael Collet <rco@odoo.com>
-
Jeremy Kersten authored
task-2086939 closes odoo/odoo#40059 Signed-off-by:
Jérémy Kersten (jke) <jke@openerp.com>
-
qsm-odoo authored
The original goal was to not have any pre-installed theme by default and to force the user to consider installing one through the customize dialog. Now that we have a system to allow switching theme, it is better to have one installed by default and allow the user to switch theme from the customize dialog (note that last part was made in the parent commit with the merge of website_theme_install into website). Note: theme_default is purely empty, it is only installed by default for clarity in the theme selection screen, for the default website.
-
qsm-odoo authored
* theme_bootswatch, theme_default, website_theme_install
-
Manuel Vázquez Acosta authored
Commit 5fcf891e introduced optimizations for name_search in several models. However, that produces some counter-intuitive searches. In a DB with project and custom data: >>> Project = self.env['project.task'] >>> Project.search([('user_id', 'ilike', 'demo')]).mapped('user_id.name') ['Marc Demo'] >>> Project.search([('user_id', 'not ilike', 'demo')]).mapped('user_id.name') ['Marc Demo'] The projects returned with 'not ilike' are a super-set of those returned with 'ilike': >>> Project.search([('user_id', 'ilike', 'demo')]) project.task(22, 21, 20, 16, 14, 13) >>> Project.search([('user_id', 'not ilike', 'demo')]) project.task(22, 21, 29, 28, 27, 26, 25, 20, 16, 14, 13, 31, 30) This commit fix this behaviour by choosing '!=' instead of '=' whenever the operator is a negation operator. The 'res.users' is more exposed than the other models touched by 5fcf891e, because user may search for 'Created by' in the web client. closes odoo/odoo#40140 X-original-commit: b3c539b0 Signed-off-by:
Yannick Tivisse (yti) <yti@odoo.com>
-
lejeune quentin authored
The self don't contain 'interface_protocol'. The 'interface_protocol' is in self.dev because we add this in 'supported' function. closes odoo/odoo#40132 X-original-commit: 6963a016 Signed-off-by:
Quentin Lejeune (qle) <qle@odoo.com>
-
Arnold Moyaux authored
commit 89f20d2c removed thumbnail but didn't adapt the views that used it. Adapt the view and directly use the datas and not the thumbnail. Close #38747 closes odoo/odoo#40126 X-original-commit: e73b468135d27ce8c1e84c3ecf2d0b3af176d760 Signed-off-by:
Arnold Moyaux <amoyaux@users.noreply.github.com>
-
Nicolas Lempereur authored
In 12.3 there was a number of changes in source mode. This was reverted before 13.0 and somehow it seems the source mode was lost between the 12.3 editor changes and its revert. With this changeset, we introduce back source mode as it was in 12. opw-2091649 opw-2116960 closes #40026 closes odoo/odoo#40120 X-original-commit: e29c0896 Signed-off-by:
Nicolas Lempereur (nle) <nle@odoo.com>
-
Swapnesh Shah authored
Fixes https://github.com/odoo/odoo/issues/39358 Before this commit Internal user (With no other Rights) cannot perform any activity on Reminder Popup due to missing rights to set calendar_last_notif_ack field. With this fix, we are now using sudo to write calendar_last_notif_ack closes odoo/odoo#40104 X-original-commit: 91560fae Signed-off-by:
Nicolas Martinelli (nim) <nim@odoo.com>
-
jvm-odoo authored
Reproduce this issue - Install CRM & Sales - Create 2 sales team in CRM settings - Create some invoices and register payments for the 2 teams - Go in CRM > Sales > Team pipelines The invoicing amount is still 0 for both teams. Cause - The `_compute_invoiced` method in `CrmTeam` models use a SQL query to retrieve the invoices lines but it returns an empty recordset because the dates are not right ordered. - The line balance are negatives values, doing a SUM() will always returns 0 This commit re-order the dates and invert the sign of line.balance. OPW-2119819 closes odoo/odoo#40115 X-original-commit: 578dacc3 Signed-off-by:
Jason Van Malder <jasonvanmalder@users.noreply.github.com>
-
Ravi Gohil authored
- fixed some tax report lines by showing correct amounts - corrected account types - set default receivable/payable/advance tax accounts for tax groups closes odoo/odoo#40114 Task: 1917932 Closes: 39191 X-original-commit: 0677d474 Signed-off-by:
oco-odoo <oco-odoo@users.noreply.github.com>
-
Yannick Tivisse authored
closes odoo/odoo#40020 Signed-off-by:
Yannick Tivisse (yti) <yti@odoo.com>
-
Yannick Tivisse authored
-
Yannick Tivisse authored
-
Yannick Tivisse authored
-
Yannick Tivisse authored
-
Yannick Tivisse authored
-
Yannick Tivisse authored
Some tests (test_00_workorder_process, ...) are executed several times, only because we extend a test class to retrieve the setUp (or setUpClass) instead of creating a common class. This could lead to issues, (like for test_00_workorder_process) depending on the installed modules.
-
Yannick Tivisse authored
Purpose ======= This module contains tests related to base automation. It makes no sense as they have no business value. Specification ============= Move all the tests to a separate module as it contains models used only to perform tests independently to functional aspects of other models.
-
Yannick Tivisse authored
-
- Oct 03, 2019
-
-
mreficent authored
closes odoo/odoo#33869 Signed-off-by:
Yannick Tivisse (yti) <yti@odoo.com>
-
- Nov 12, 2019
-
-
Thibault Delavallée authored
A patched method was not unpatched. Which triggered issues in a staging master branch trying to untie a bit mail tests. closes odoo/odoo#40099 X-original-commit: 5dbf4c56 Signed-off-by:
Xavier Dollé (xdo) <xdo@odoo.com>
-
Andrea Grazioso (agr-odoo) authored
Install stock and sale. Create a sale with 2+ products, save and confirm. Look for the created picking. There will be no source doument, because of cb618e9a the behavior has changed when there are multiple source document, possibly to avoid displaying the wrong source if they differ. Adding the possibility to display multiple source documents, eventually truncating the list opw-2117886 closes odoo/odoo#40098 X-original-commit: baad02d0 Signed-off-by:
Nicolas Martinelli (nim) <nim@odoo.com>
-
- Nov 08, 2019
-
-
Yannick Tivisse authored
Purpose ======= Steps to reproduce: - Configure a product of type service to create a task on a sales order validation, without configuring a project template - On the SO confirmation, the project is generated without any stages Additional issue: - go to the Kanban view of the Project - filter on something that doesn't give any result - The kanban switches to edit mode, even if there is a task This commit solves both issues. closes odoo/odoo#40057 X-original-commit: e2de6331f7f75c9c9b086e57b88f6d25a2cd303d Signed-off-by:
Yannick Tivisse (yti) <yti@odoo.com>
-
Vishnu Thuletiya authored
The icon of the 'Vendor Bills' stat button isn't displayed so fix the icon class. Task-2115206 closes odoo/odoo#40050 Closes: #40006 X-original-commit: 5a595c59 Signed-off-by:
Yannick Tivisse (yti) <yti@odoo.com>
-
Yannick Tivisse authored
Purpose ======= If the user creates a task and if the project isn't set, then all the stages that are not linked to a project are displayed, which is polluting the form view. Specifications ============== If no project is set on the task form view, do not display any stages in the statusbar. closes odoo/odoo#40041 Signed-off-by:
Yannick Tivisse (yti) <yti@odoo.com>
-
- Nov 06, 2019
-
-
Martin Trigaux authored
In 13.0, we use the IoTBox which handle https correctly 12.0 was still a transition version but people should have switched in 13.0 closes odoo/odoo#39845 X-original-commit: 5d44adcd Signed-off-by:
Martin Trigaux (mat) <mat@odoo.com>
-
- Nov 08, 2019
-
-
wan authored
Task 2076244 Commit 4a1bbbff added that but it had to be reverted because it didn't take into account the periodicity of the tax return of the company and because it added the period for all mail.activity closes odoo/odoo#38199 Signed-off-by:
Quentin De Paoli (qdp) <qdp@openerp.com>
-
- Nov 10, 2019
-
-
Wolfgang Taferner authored
In case of a multi-record and multi-page (i.e. 2 pages per PDF) report the assertion is triggered b/c we have 4 pages and only two records with a PDF of 2 pages each, so the outline_page needs to be unique before assertion. len([0, 0, 2, 2]) != len([record_id1, record_id2]) len([0, 2]) == len([record_id1, record_id2]) closes odoo/odoo#40076 X-original-commit: 573e5777 Signed-off-by:
Nicolas Martinelli (nim) <nim@odoo.com>
-
- Nov 12, 2019
-
-
Andrea Grazioso (agr-odoo) authored
Activate Google Synchronization, create on OE a recurrent event, synchronize the calendar, then delete an event of the recursion on GC, sync again on OE. The event will be deleted from GC but not from OE after sync. This appens because of this "rewrite" rule https://github.com/odoo/odoo/blob/12.0/addons/calendar/models/calendar.py#L918 that occur on event creation from OE, altering the event parameters when is marked "allday". When an "allday" event is deleted from GC the unlink is triggered in OE with the default time "00:00:00". During the creation of the exclusion ' _inverse_dates' will be called altering start and stop datetime but not recurrent_id_date, so the new record will not match the event generating the recursion and the exclusion will not occur. The problem require particular carefulness because when a recurrent event is fetched from google the '_inverse_dates' is not called, so in that case the default time is fine. opw-2060526 closes odoo/odoo#39662 Signed-off-by:
Nicolas Martinelli (nim) <nim@odoo.com>
-
- Nov 08, 2019
-
-
Victor Feyens authored
closes odoo/odoo#40047 X-original-commit: 4640ea40 Signed-off-by:
Victor Feyens (vfe) <vfe@odoo.com>
-
lejeune quentin authored
closes odoo/odoo#40044 X-original-commit: 98f48141 Signed-off-by:
Quentin Lejeune (qle) <qle@odoo.com>
-
jvm-odoo authored
Prerequisites - Configure a mail server (incoming) - Enable leads in CRM app - Create a sales team with a mail alias (ex: testcrm@odoo.com) and check "Pipeline" and "Leads" - Set a partner email with one of yours (ex: bob@odoo.com) /!\ - Send a mail from bob to testcrm - In the incoming mail server click on "Fetch" Reproduce the issue: - Convert the generated lead to an opportunity - Choose "Existing customer" and set another one than the actual - The opportunity is created but the customer is the old one Cause: The given partner_id is overriden by the old one in the `handle_partner_assignation` method. This commit gives the priority to the new partner_id. OPW-2089404 closes odoo/odoo#40031 X-original-commit: e1833936 Signed-off-by:
Jason Van Malder <jasonvanmalder@users.noreply.github.com>
-
Christophe Monniez authored
Since the deployement of the forward-port bot, chances to merge code with conflict markers has greatly increased. With this commit, a new test is added to grep for those markers in most common code files. closes odoo/odoo#40029 X-original-commit: 19bf61c0 Signed-off-by:
Christophe Monniez (moc) <moc@odoo.com>
-
mreficent authored
Firstly bd49f9fd did some fixes that removed a bunch of code containing 'install_mode_data'. Later, 627292f7 replaced 'install_mode_data' for 'install_filename'. Finally, 43dd9ecd reverted bd49f9fd (including 'install_mode_data' remnant). closes odoo/odoo#40027 X-original-commit: 0c3d9256 Signed-off-by:
Yannick Tivisse (yti) <yti@odoo.com>
-
Victor Feyens authored
closes odoo/odoo#40025 Signed-off-by:
Victor Feyens (vfe) <vfe@odoo.com>
-
Victor Feyens authored
-
xmo-odoo authored
The third parameter to assertAlmostEqual is a precision (places), not the assertion message. This goes unnoticed when using two objects which are strictly equal because assertAlmostEqual shortcuts if the two inputs are equal, before falling back on approximation. Since the parameters here are two integers, they're always going to be either identical or completely different, therefore the issue is only visible if the assertion fails, hiding the assertion error. * pass the message by keyword * replace assertAlmostEqual by assertEqual as the inputs are integers and integers can't really be "almost" equal closes odoo/odoo#40030 X-original-commit: f22e7177 Signed-off-by:
Xavier Morel (xmo) <xmo@odoo.com>
-
Antoine Prieels authored
Updates to the customer display were sent too often: - Twice when creating a new order - Twice when removing a payment line - Every time the status of a payment line with a terminal changed closes odoo/odoo#40024 X-original-commit: b72b08cf Signed-off-by:
Quentin Lejeune (qle) <qle@odoo.com>
-
- Nov 07, 2019
-
-
qsm-odoo authored
When the user changed the parallax option, it was only updated on save. So, the user was not able to have a preview of what he chose. Note: this commit is made in saas-12.3 but does not fully solve the problem there... and unfortunately I don't know why. It fully solves the problem in 13.0 though and this is more important. closes odoo/odoo#39995 X-original-commit: 4b633949cd4fd1cae807b95d233879ac4adc01ce Signed-off-by:
Quentin Smetz (qsm) <qsm@odoo.com>
-