Daily updates from Odoo
Navigate
Branch
Tuesday, February 6, 2018
14 changes
Enhancements to existing features
Several Odoo apps now provide a better default card-style view for mobile users, making key records easier to browse and act on from smaller screens. This improves day-to-day usability across accounting, inventory, HR time off, products, website, and sales workflows without changing core business processes.
Original PR description
Task : https://www.odoo.com/web#id=40281&view_type=form&model=project.task&action=327&menu_id=4720 Pad : https://pad.odoo.com/p/r.4cf49ea51ed955d316eac91c09353820 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Project screens were adjusted to make editing and reporting easier, including clearer pivot report grouping and visible assignee information. Kanban columns also avoid redundant record-count tooltips when a progress bar is already present, reducing visual clutter for users.
Original PR description
Task : https://www.odoo.com/web?#id=54027&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720 Pad : https://pad.odoo.com/p/r.394011d9fd84ee9ca8fb5f7418bcf9c8 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This change standardizes how purchase order and purchase order line preparation methods receive information. It improves maintainability and reduces the risk of inconsistent behavior in purchasing workflows, with no expected direct change for everyday users.
Original PR description
Make `_prepare_purchase_order` and `_prepare_purchase_order_line` using consistent parameters. opw-806807 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
Online quotation templates now avoid repeating the same product description when several variants of one product are included. This makes quotes easier for customers to read while still showing the variant details that distinguish each option.
Original PR description
Description of the issue/feature this PR addresses: <b> Task:</b> https://www.odoo.com/web?#id=33625&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720 <b> Pad:</b> https://pad.odoo.com/p/r.c78abbb5a742d49246aac75f16f364b5 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
Sales and invoice reports now show the tax amount on each line when taxes are rounded per line. This makes totals easier to understand and helps users verify tax calculations more clearly on customer and compliance documents.
Original PR description
… rounding method is per line Description of the issue/feature this PR addresses: When tax rounding is per line show tax amount on invoice report for more clarity Task: https://www.odoo.com/web?#id=31052&view_type=form&model=project.task&action=327&menu_id=4720 Pad: https://pad.odoo.com/p/r.e93e5464ecbe7d21cd83491aca33adb2 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
Deleting a stage that still contains related work items or records is now blocked, preventing records from ending up in unclear or undefined states. In projects, shared stages can be removed from a specific project when unused there, while still protecting stages that contain active or archived tasks.
Original PR description
Task : https://www.odoo.com/web?debug#id=33826&view_type=form&model=project.task&action=327&menu_id=4720 Pad : https://pad.odoo.com/p/r.26ad66330add3cb395159f9f31bcf128 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
Users can no longer accidentally delete a Kanban stage that still contains active records, reducing the risk of disrupting project workflows. The change also improves how deletion context is handled across Kanban, list, and form views so stage deletion behaves more safely and consistently.
Original PR description
Task : https://www.odoo.com/web#id=33826&view_type=form&model=project.task&action=327&menu_id=4720 Pad : https://pad.odoo.com/p/r.26ad66330add3cb395159f9f31bcf128 Description of the issue/feature this PR addresses: Current behavior before PR: User inadvertently delete a stage having active records.. Desired behavior after PR is merged: Restrict user to delete stage in kanban containing active records. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Email marketing reports now include the number of clicks in the pivot table. This gives teams a fuller view of campaign engagement directly in reporting, matching the metrics already visible on individual mailing records.
Original PR description
Description of the issue/feature this PR addresses: Task ID - https://www.odoo.com/web#id=34625&view_type=form&model=project.task&action=327&menu_id=4720 PAD - https://pad.odoo.com/p/r.acb94d4413217e85550ef77125451da4 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
Helpdesk team settings now include calendar-related configuration, making it easier for teams to manage scheduling from the same setup area. This helps support teams align ticket handling with appointments or planned activities without extra navigation.
Original PR description
Task ID - https://www.odoo.com/web#id=36965&view_type=form&model=project.task&action=327&menu_id=4720 Pad - https://pad.odoo.com/p/r.a8472cfacf8a80bfcaf9db3b2df630ba
Deleting a workflow stage is now blocked when tickets, engineering changes, quality checks, or similar records still use it. In Helpdesk, shared stages can be removed from a team when unused there, while still protecting records in other teams from ending up in an unclear undefined column.
Original PR description
Task : https://www.odoo.com/web?debug#id=33826&view_type=form&model=project.task&action=327&menu_id=4720 Pad : https://pad.odoo.com/p/r.26ad66330add3cb395159f9f31bcf128
Newly created actions from Studio now show the updated empty-state layout, including a friendly smiling document icon. This creates a more consistent and polished experience when users open views that do not yet contain records.
Original PR description
Task: https://www.odoo.com/web?#id=51521&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720 Pad: https://pad.odoo.com/p/r.3ad52e0683d8ec8c8b79693157effda3
Resolved issues and error corrections
This fixes how forum post information is shown after a user publishes content with images. It makes the forum posting experience smoother and helps ensure newly posted content appears as expected.
Original PR description
Task: https://www.odoo.com/web#id=34691&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720 Pad: https://pad.odoo.com/p/r.eadde644a7e0ea0c88060b9400330750
This change removes an unnecessary title from a payment-related error message. It makes the warning clearer and more consistent for users without changing payment processing behavior.
Original PR description
Issue : https://www.odoo.com/web#id=806216&view_type=form&model=project.issue&action=609&menu_id=4720 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update makes the status titles shown on purchase order documents more precise. It helps vendors and suppliers better understand the current state of a purchase order, reducing ambiguity in business communication.
Original PR description
@tivisse As you were the latest to modify this part of the code may I ask you to merge this and therefore improve the communication? This is the result of a discussion with a client and I think it is good to be precise here as it is part of the communication with the vendor/supplier and Thank you in advance...it could be eventually also merged in stable but the change of the little condition which might be inherited by someone made me decide to suggest for master. @nim-odoo if you think it is bearable (helping more than disturbing some inheritance in case of an upgrade of the module) in stable feel free to grab it and merge there (same patch is working for both) -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr