Avoid sharing of users'groups when writing on multiple users.
When changing groups of multiple users, all implied groups were shared
between written users.
Oversight of new-api rewrite.
Fixes#26036
The 'drag and drop' function defined in test_utils should be aware of four
different cases, moving up or down, above or below another row.
We need an offset of one pixel for the function to work when moving down
(this is a case of broken symmetry because of <=)
Related to opw 1867049 regarding sequences of resequence moves.
Steps to reproduce the bug:
- Go on a picking with an operation type of type "vendor" (e.g. a receipt) :
the field source location appears while it should be the destination location.
- Go on a picking with an operation type of type "customer " (e.g. a delivery) :
the field destination location appears while it should be the source location.
opw:1869145
We need to be able to filter and group by campaign_id, source_id and
medium_id in the sale_report those fields are defined in utm mixin which
is installed with website_sale_link_tracker.
With BS4, I had to change the dropdown structure and with it the messy
way we handled "selected" items. Sub-filters items were still not
adapted correctly: use the "selected" class on dropdown-item elements,
not one of its parent.
In crm,website_crm_partner_assign and website_crm_score there were fields with
almost the same label, which was confusing, we change those names so it
reflects better what the field is used for.
| field | module | old label | new label |
------------------------------------------------------------------------------------------
| date_open | crm | Assigned | Assignation Date |
| date_assign | website_crm_partner_assign | Assignation Date | Partner Assignation Date |
| assign_date | website_crm_score | Assign Date | Auto Assign Date |
------------------------------------------------------------------------------------------
In order to be able to add some enterprise views to crm, we need to
define the views as act_window.view, we also want to define a graph and
a pivot view for the leads.
We also want to have a more powerful search view associated with these.
Task: #1831168Closes#25400
Purpose
=======
More and more features redirect to the portal (see & pay
quotations, invoices, etc.) with anonymous access by default
you can't sign up to the customer portal, while you see
a Sign in button. It's frustrating.
The ability to create a customer account is a nice service,
useful in any business willing to engage with returning
customers. This should be the default value
Specification
=============
Activate B2C portal by default. We have to create an
ir.config.parameter for the change to be immediate after
the installation. Otherwise the admin has to go and save
its res.config.settings one time before it's effective.
Task ID: 1841514
Purpose
=======
The only module that was supposed to work without the accounting menuitems was
the ecommerce. Now that the ecommerce wants the accounting menuitems to be
visible, this module makes no sense anymore.
Specification
=============
Remove the account_invoicing module and move the code to account.
Purpose
=======
Add account invoicing dependency and remove some duplicate options
Purpose of this commit is when ecommerce installed lots of invoicing
stuff still show up while account_invoicing is not yet installed
(like (invoice button in sales order, invoicing policy of products etc..)
and most of customers not using ecommerce without invoicing so the split is
useless for now
Specification
=============
Add account_invoicing as a dependency of website_sale and remove
the duplicated options from settings
Related Task ID: 1866823
The database manager was broken with BS4, this commit restores it. The
old BS3 layout was not perfect either, so this commit redesigns the
forms with BS4 too.
3869cdf7d8 merged a fix which used a
P3-style super call, which is not compatible with Python 2.
While 11.0 is not really exactly officially supported on Python 2,
we originally decided not to break compatibility unless there were
very good reasons to do so.
Steps to reproduce:
1. Activate multi-currency and associate a price list "Other list" with secondary currency as an alternative for "Public Price List".
2. Enable the price list to be selectable on the website.
3. Enable wishlist functionality on Website module
4. Navigate to website without logging in
5. Add a product to the wishlist (with the default price list)
6. Switch price lists.
Bug:
The wrong currency was displayed in the wishlist for the new price.
PS: In function "compute_new_price", price_new = website_price
opw:1867314
With 60300fc, people can use promo code on website.
But the condition leads to a side effect, if a partner has a pricelist set for
him, he will never be able to see the dropdown list of pricelist since he will
enter the else condition with show_visible set to true.
Now, user is able to see selectable pricelists.
opw-1869371
Have a statement line with multiple pages of propositions
Go to the last page
Add everything
Before this commit, after clicking on the last item of the list,
a write-off creation was displayed, without any means to come back to the other
propositions
After this commit, we display the page before
In manual reconciliation, have an accound with no direct proposal.
An empty line should be present
Click on it
Before this commit, there was a traceback
After this commit, a write-off creation appears
In manual reconciliation (but probably automatic too)
Have 3 lines for one account
2 of them are balanced
the third is of an amount X
Add the three lines to the reconciliation
A write-off proposal of -X should appear
Now, remove the third line by clicking on it
Click on Reconcile
Before this commit, the values sent to the server were wrong, as the write-off
was still included
After this commit, we make sure we don't send lines that are not displayed
Create an account.move, create a line, then add an item to start to add a second aml
The current balance of the move is put in debit (or credit) to help automatically making the second line
Save the move.
Edit the move
Delete a line
Add a new line
Before this commit, the balance was not correctly computed because the default_get did not compute
the balance on deleted lines
The move ended up with wrong unbalanced new lines
After this commit, the balance is computed with deleted lines taken into account
This is a standard BS4 bug: radio buttons's dot is not properly centered
as soon as the html font-size is not a multiple of 4 (and our backend
uses 13px). As a quick fix, I change that to 12px and use a font-size base
of 13/12rem so that the body font-size does not change. Bootstrap will
probably fix this in a future update.
Let's consider the partner P1 with the address A1 and its invoice partner P2
with the address A2.
When creating a transaction in the shop for P1 with billing address = A1:
- if option Payment Flow = Redirection to the acquirer website
=> the billing address of the transaction is A1
- if if option Payment Flow = Payment from Odoo
=> the billing address of the transaction was A2
Now with this patch, the billing address is A1 in each case.
opw:1867188
Purpose
=======
Improve some common usability issues coming from the invoicing followup.
Specification
=============
1. Sale: Rename 'Check/Set Price' buttons for more clarify
relabel "Check price" -> "Get rate"
relabel "Set Price" -> "Add to order"
2. Sale: Change the default invoicing method if there are downpayments
Purpose
-------
Currently the default invoicing method is not very clear.
Specification
-------------
Currently the result is not really correct. We can propose to deduct
the down payment even if there are no down payments on the sales order.
Now the option to deduct down payments will be selected if there
is a downpayment line on the sales order and if there exists at
least one invoice linked to the sales order that is not cancelled.
3. Delivery: Improve the SO invoice status
Purpose
-------
If a SO is only containing lines for which the product is invoiced on
the delivered quantity, the sales order is marked as 'Nothing to Invoice'.
If I add a delivery line, the SO becomes 'To Invoice'. There is not really
a use case in the real life where you will invoice the delivery fees before
invoicing what has been really delivered.
Specification
-------------
If an order:
- contains delivery lines or downpayment lines
- If the product on the other lines are invoiced on the delivered quantity
- Nothing has been delivery or can be invoiced for theses lines
Set the invoice status of the sales order to 'Nothing to invoice' instead
of 'To Invoice'
4. Sale: Unlink the down payment on a SO if the invoice is unlinked
Purpose
-------
When we create a downpayment line of SO and when we delete Invoice of downpayment then so line for downpayment is not deleted.
Specification
-------------
Remove the downpayment line in the SO if the related invoice is deleted
Task ID :33126
Purpose
=======
When we create a downpayment line of SO and when we delete Invoice of downpayment then so line for downpayment is not deleted.
Specification
=============
Remove the downpayment line in the SO if the related invoice is deleted
Task ID :33126
Purpose
=======
If a SO is only containing lines for which the product is invoiced on
the delivered quantity, the sales order is marked as 'Nothing to Invoice'.
If I add a delivery line, the SO becomes 'To Invoice'. There is not really
a use case in the real life where you will invoice the delivery fees before
invoicing what has been really delivered.
Specification
=============
If an order:
- contains delivery lines or downpayment lines
- If the product on the other lines are invoiced on the delivered quantity
- Nothing has been delivery or can be invoiced for theses lines
Set the invoice status of the sales order to 'Nothing to invoice' instead
of 'To Invoice'
Task ID : 33126
Purpose
=======
Currently the default invoicing method is not very clear.
Specification
=============
Currently the result is not really correct. We can propose to deduct
the down payment even if there are no down payments on the sales order.
Now the option to deduct down payments will be selected if there
is a downpayment line on the sales order and if there exists at
least one invoice linked to the sales order that is not cancelled.
Task ID : 33126
Before this commit, negative values in a float field interpreted as time
(i.e. unit_amount on analytic lines) were wrongly formatted
After this commit, not only we correct the hr_timesheet qweb templates
but we also correct the qweb widget to handle the case
OPW 1869986
closes#26024
Modal footers now use flex to vertically center buttons. So our
left-align style overridde had to be adapted. Also, we sometimes
use footer buttons as non-direct children of the modal-footer, which
is not a supported BS4 case, so we had to adapt that too.
Nikunj Ladava