Daily updates from Odoo
Thursday, December 1, 2016
9 changes · master
Enhancements to existing features
The planner is now shown only to administrators and users with system settings permissions. This prevents regular users from seeing planner links that lead to actions they are not allowed to perform, reducing confusion and access error messages.
Original PR description
Description of the issue/feature this PR addresses: Task : https://www.odoo.com/web#id=29170&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720 Pad : https://pad.odoo.com/p/r.510868f80e29f20b1ea7ad922a1a4579 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
Journal entries now show a history area with clickable links to the original documents that created them, such as invoices or stock pickings. This makes it easier for users to trace accounting entries back to their business source, especially in perpetual inventory workflows.
Original PR description
Description of the issue/feature this PR addresses: - In a perpetual inventory mode, it is not possible to reach the picking/Invoice from the journal entry view because the ref field is not clickable so add chatter to get the history (which doc created the move) and being able to go to the move from the chatter. Current behavior before PR: - Currently there is not any chatter for getting history so you can not go origin document. Desired behavior after PR is merged: - Now It is possible to go origin document because of adding of chatter in journal entry view and its history is clickable. ## I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr … journal entries. Task : https://www.odoo.com/web#id=27307&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720 Pad: https://pad.odoo.com/p/r.358dc3212d75e1bb5110af1aba4c7233
Product variants can now have their own vendor prices, separate from the main product template and from other variants. Purchase requests will use a variant-specific vendor price when available, helping buyers create more accurate RFQs and reducing pricing confusion.
The purchase order fiscal position field no longer offers a create-and-edit option, helping users follow the intended setup flow. Empty dropdown searches now display “No result to show” without link-style coloring, reducing confusion from text that looked clickable but was not.
Original PR description
Description of the issue/feature this PR addresses: - when no result found in Many2one fields it will show string 'No Result to show' in link color, it gives the user to click on that text. - In purchase app Fiscal position field show 'Create and Edit' option. Current behavior before PR: - When no result found in Many2one fields it show 'No result to show' string in color. - In purchase app Fiscal position field show 'Create and Edit' option. Desired behavior after PR is merged: - Now when no result found in Many2one field color remove from 'No result to show' string. - In purchase app 'Create and edit option' remove from Fiscal Position field. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Task : https://www.odoo.com/web?#id=29214&view_type=kanban&model=project.task&action=327&menu_id=4720 Pad : https://pad.odoo.com/p/r.4f041c2ab727ff572a0313a8dd075baf
The events page now shows pagination at the bottom of the event list, making it clearer when more results are available after browsing. This helps visitors continue to the next page without needing to scroll back up or miss additional events.
Original PR description
Description of the issue/feature this PR addresses: Task:https://www.odoo.com/web#id=29555&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720 Pad: https://pad.odoo.com/p/r.ea190149ab94911ac2a445af2fff9543 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 … page.
Product variant pages now prevent users from directly changing attribute values. This reduces the risk of inconsistent product data and avoids issues caused by editing variant-defining details in the wrong place.
Original PR description
Description of the issue/feature this PR addresses: Task: https://www.odoo.com/web#id=29192&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720 Pad: https://pad.odoo.com/p/r.adcc86df75badb8d5b5bd627c2eb25a8 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
Menu labels previously called “Reports” are renamed to “Reporting” across many Odoo apps to better distinguish analytical dashboards from printable reports. This makes navigation clearer for business users looking for reporting views versus generated documents.
Original PR description
Task: https://www.odoo.com/web#id=28617&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720 Pad: https://pad.odoo.com/p/r.e621b143826d0115d2e323cdbb92c2cd 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
Several menu labels previously called “Reports” are now named “Reporting” in Helpdesk, Appraisals, Sales Contracts, and Studio. This makes analytical reporting areas easier to distinguish from printable business reports, reducing confusion for users navigating the system.
Original PR description
Task: https://www.odoo.com/web#id=28617&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720 Pad: https://pad.odoo.com/p/r.e621b143826d0115d2e323cdbb92c2cd
Resolved issues and error corrections
Rating feedback pages and emails now appear in the recipient partner's preferred language instead of defaulting to the administrator's or sender's language. This improves customer experience and avoids confusing multilingual communications.
Original PR description
Several translation issues are faced with the rating module: - the feedback page is always displayed in the admin language - the feedback emails are always sent in the user's language One would expect these to be in the partner language. opw-694718