Daily updates from Odoo
Tuesday, August 21, 2018
5 changes
Enhancements to existing features
Project tasks can now show the main company or customer associated with a contact. This makes it easier for teams to filter and group tasks to get a unified view of work for the same customer, even when tasks are assigned to individual contacts.
Original PR description
Before this commit, in the case where tasks where assigned to contacts, it was very cumbersome to get a unified view of one customer. Now, commercial partner is set as a task column and as such available on filters and groupings. Note: This is a basic step towards such feature, maybe UX needs to be tweaked further. (eg. hide commercial partner field if it doesn't differ from partner - not sure how to implement that properly) It's probably just a first step in the right direction... -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Invoices and sales reports no longer show tax groups whose total amount is 0.00. This reduces confusion for customers by hiding tax lines that do not affect the final amount due.
Original PR description
In some cases, a tax can be applied as a calculatory group, where two child elements zero out each other. In such case, where the total group amount would result in 0.0, we don't want to display this…
In some cases, a tax can be applied as a calculatory group, where two child elements zero out each other. In such case, where the total group amount would result in 0.0, we don't want to display this group. Doing so would be confusing to the spectator. After this commit, this confusion is relieved. **Description of the issue/feature this PR addresses:** - 0.0 results of tax groups generate confusing UI on printed invoice **Current behavior before PR:** - (Calculatory) Tax groups resulting in 0.0 total are printed on inovices **Desired behavior after PR is merged:** - (Calculatory) Tax groups on invoices, resulting in 0.0, are not printed in invoices as they are not relevant to the recipient (after all they don't have any effect on the transaction sum). **Note:** Please do not close, even if not immediately accepted (`wishlist` tag). This PR is meant to be carried along and actively maintained, until this semantic will be completed this way or another. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr @xoe-labs
Custom models can now use an active status so records can be archived and filtered consistently in the web interface. This helps businesses manage custom data without losing records, while keeping inactive items out of day-to-day views.
Original PR description
Towards solving #26162 This PR does not include: - ~Necessary changes to WebClient~ (ed865af1610) - Necessary changes to Studio - Safeguards on UX (`x_active` can only be Boolean) - Tests One alternative implementation: - Add `active` as a base model field. Similar to what the chatter field checkbox does. - But: Side effects of being a `base` field with no underlying python code?? -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Traceability reports are now available for manufacturing orders even when the finished product is not individually tracked, making it easier to follow component and production history. The update also improves report accuracy, clearer clickable links, and replaces lot-related sales and purchase lists with easier navigation buttons.
Original PR description
Task: https://www.odoo.com/web#id=1873101&model=project.task&view_type=form&menu_id=
The generic tax report now includes a dedicated Tax Adjustment section alongside Sales and Purchases. This makes tax adjustments easier to identify and review in financial reporting, supporting clearer compliance and accounting workflows.
Original PR description
Task : https://www.odoo.com/web#id=38076&view_type=form&model=project.task&action=327&menu_id=4720 Pad : https://pad.odoo.com/p/r.713cb06bbfa13a95a32983e4a7b37bd6 Description of the issue/feature this PR addresses: On the generic tax report, create a section "Tax Adjustment" (same level than Sales and Purchases sections) Current behavior before PR: On the generic tax report, there is no "Tax Adjustment" (same level than Sales and Purchases sections) Desired behavior after PR is merged: On the generic tax report, create a section "Tax Adjustment" (same level than Sales and Purchases sections)