Daily updates from Odoo
Tuesday, November 5, 2019
6 changes · master
Enhancements to existing features
Website profiles can now rank users by recent karma gains for the past week or month, in addition to total karma. This helps communities highlight currently active contributors while keeping the tracking data consolidated and private.
Original PR description
PURPOSE Allow karma gain tracking enabling notably display of top users based on weekly / monthly gain in website profile. SPECIFICATIONS Each time a user gains karma a record is created in the gamification karma tracking model. Scheduled activity runs to consolidate the records into monthly gain records to avoid having crowdy table and unnecessary noise in karma gain. This model is made private and only accessible through some dedicated compute methods / controllers used in website profile. In website profile module buttons are added to see users ranking based on their total karma (like before) but also by last week and last month gains (using the newly introduced tracking model). Some fixes are provided in this merge as well as tests. LINKS Task ID 2003505 PR #34594
Changes made to down payment invoices, such as taxes or amounts, are now reflected back on the related sales order when the invoice is posted. This keeps sales order totals and final invoice calculations accurate, especially when down payments are partially or fully refunded.
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
The point-of-sale payment screen now shows the total, amount due, and change in one clear area instead of scattering values across payment lines. It also improves handling of electronic terminal payments so pending or invalid payments are not double-counted or saved by mistake.
Original PR description
The previous behavior is that the change is displayed at each payment line and the remaining is displayed at the bottom. Also, total amount is lost in the screen. This commit addresses this issue by showing the values of remaining amount and change at just one area of the payment screen. TASK-ID: 1984690 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Bank statements can now automatically fill starting and ending balances from the previous statement, helping avoid gaps between statements. This improves usability for imported or synchronized statements and keeps later statements aligned when a statement is inserted between existing ones.
Original PR description
To prevent having holes between statements and for better usability using import and synchronization we try to automatically set the starting and ending balance based on the previous existing statement. To do that, we added a new field previous_statement_id so that whenever we change the ending_balance of the previous statement, we recompute the starting balance and ending balance of the current statement. Also creating a new statement in between 2 others statements will automatically set the correct value to the starting and ending balance of that statement and all the statements afterwards. Exception: creating a statement by hand won't automatically set the balance_end_real, however if you create one between 2 statements, the balance_end_real of next statements will be recomputed -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Users can now start reconciliation directly when viewing a specific partner in the partner ledger. This reduces extra navigation for accounting teams and makes it easier to clean up partner balances from the report context.
Original PR description
Task [2092080](https://www.odoo.com/web#id=2092080&action=333&active_id=967&model=project.task&view_type=form&menu_id=4720) Allow reconciling entries for a dedicated partner when we are browsing their data in the partner ledger. The template was already correct in `account_reports.line_template_partner_ledger_report` but the needed value partner_id was never set in _get_report_line_partner
Resolved issues and error corrections
Online bank synchronization now groups imported transactions by their actual transaction dates instead of only looking at the most recent statement. This prevents transactions from being placed in the wrong daily or periodic statement and may reopen a posted statement when a matching transaction needs to be added.
Original PR description
Previously we were splitting transactions in the following way: We only checked the last statement date and based on the split frequency we decided if we had to create a new statement or not. We did not take into account the transactions date at all, which means that it was possible to have daily statement with transactions from another date. Now we base ourselves on the transactions date and we move each transactions to the correct statement based on the spit frequency. -> This implies some changes, if the transactions has to be put in a posted bank statement, we will add the line inside and reset the statement to 'draft'. Other transactions will be created in new statements which can possibly be between two others statements.