Thursday, April 13, 2023
39 changes · master
Enhancements to existing features
Advanced search and filtering tools were updated across Spreadsheet, Map, and Studio areas to stay aligned with the latest search behavior. Users should see smoother handling of complex filters, including clearer reset options when a filter cannot be supported.
Task lists for main tasks, sub-tasks, and blocked-by items now use the same layout. This makes project information easier to compare and ensures future list changes apply consistently across related task views.
Original PR description
Purpose of this commit have consistent list views between project.task and the sub-tasks / blocked by o2m so that when a change is done in one place it also impacts the other places. So, in this commit add/update sub-task and blocked by page list views to make them identical. task-3165202
Employee names are now shown more consistently across HR-related screens using the same avatar-style display. This makes it easier for users to recognize employees quickly and creates a more uniform experience across approvals, appraisals, payroll, referrals, and Belgian payroll workflows.
Original PR description
linked to pr https://github.com/odoo/odoo/pull/111817 https://www.odoo.com/web#id=3132728&menu_id=4720&cids=1&action=333&active_id=1251&model=project.task&view_type=form
The planning dialog now shows only time slots that match the roles assigned to the selected resource. This helps users find suitable planning options faster and reduces confusion from unrelated slots.
Original PR description
Before this commit plan dialog in planning gantt view show all the slots for any resources and it may cause problems to user because user has to find slots that are resource related. This commit add a domain in plan dialog to see slots that have role in resource roles this way user only see slots that are actually gonna usefull for resource. task-2888248
The timesheet unit timer display has been adjusted so its toggle button takes up less space. This provides a cleaner, more compact layout for users entering or reviewing timesheets.
Original PR description
We have added the o_field_timesheet_uom class in the timesheet_uom_timer widget,this class reduced the width of the toggle button. task-3251667
Users can now select a helpdesk ticket directly from the timesheet timer when the chosen project is linked to a helpdesk team. This makes it easier to track time against support work while keeping the interface focused by showing either task or ticket fields as appropriate.
Original PR description
Currently the timer can be sarted only on task and project from timer header component. In this comment, if the project has a link to the helpdesk team, the helpdesk ticket field will appear in the timer header component. If the helpdesk does not have access, the user will not see the helpdesk ticket. If project is selected then helpdesk ticket field will appear. Both task and helpdesk ticket fields will not appear simultaneously. task-2829389
Payroll salary attachment records no longer mark a file upload field as tracked, because Odoo does not record changes to binary files in the chatter. This avoids misleading configuration and keeps payroll record tracking aligned with what the system can actually display.
Original PR description
before this commit, tracking is enable for the binary field, but odoo is not tracking binary fields to the chatter. after this commit, the tracking attribute is removed from the binary field w.r.t: https://github.com/odoo/odoo/commit/8506b9d62680f5e4d4cbd06359045e33920e5b66
Resolved issues and error corrections
The payroll calendar display has been reverted to its previous behavior because the earlier change caused more problems than it solved. This helps avoid confusion or incorrect calendar options when managing payroll structures.
Original PR description
This reverts commit 21e487fcfd62a8e71ccd1884ad571e04fc8fcc53 introduced in #37334. This change was bringing more issues than it was trying to solve. task-3254874 odoo/odoo#117663
Features or functions removed from Odoo
The Studio navigation bar no longer includes the shortcut to Notes. This simplifies the Studio interface by removing an entry point that is no longer needed, with minimal impact on day-to-day use.
Original PR description
This commit simply removes the notes shortcut of the studio navbar. opw-3259540
Code cleanup and technical improvements
Several enterprise apps were adjusted to stay compatible with an underlying interface change for on-screen popovers. This keeps features such as follow-ups, appointments, documents, knowledge, project planning, Gantt views, and Studio approvals working consistently without changing the user-facing workflow.
Original PR description
odoo/odoo#118066
Miscellaneous changes
Some customers in Austria are exporting their data using the DateV export available in `l10n_de_reports`. We can show the button for all DACH countries (countries where DateV is active) In the future, we shoud get this logic out of the German module, and make sure that it works for all of these countries. Forward-Port-Of: odoo/enterprise#38502
Original PR description
Some customers in Austria are exporting their data using the DateV export available in `l10n_de_reports`. We can show the button for all DACH countries (countries where DateV is active) In the future, we shoud get this logic out of the German module, and make sure that it works for all of these countries. Forward-Port-Of: odoo/enterprise#38502
This update makes many Odoo Enterprise apps more explicit about whether posted messages contain formatted content or plain text. It helps ensure message text is displayed safely and consistently across business workflows such as accounting, helpdesk, delivery, documents, HR, and appointments.
Original PR description
Enterprise part of odoo/odoo#111850 When using message_post, the body format must be explicitly specified. If html is expected, a Markup object should be used. If text is given, the content will be escaped.
This change fixes a small issue that could affect the emoji picker when replying to social stream comments. It ensures the picker receives the correct page element, improving reliability without changing the user workflow.
Original PR description
`useRef()` hook should only be used in `setup()` of component. The `add()` function of emoji picker can be used anywhere. This commit fixes the issue by limiting use of `add()` to pass Object whose `el` is an element. We should pass the ref immediately rather than the refName. https://github.com/odoo/odoo/pull/118293
It's possible to open a "Bar" without setting up the floors and tables. In this situation, we still want to see that is being sent to the preparations display. This commit fixes that behavior. First, we fix the traceback caused by sending undefined 'pos_order_id' in creating the preparation display order records. Then, when fetching the display orders, we also fetch those that are not linked to pos.order. Forward-Port-Of: odoo/enterprise#39705
Original PR description
It's possible to open a "Bar" without setting up the floors and tables. In this situation, we still want to see that is being sent to the preparations display. This commit fixes that behavior. First, we fix the traceback caused by sending undefined 'pos_order_id' in creating the preparation display order records. Then, when fetching the display orders, we also fetch those that are not linked to pos.order. Forward-Port-Of: odoo/enterprise#39705
Steps to reproduce the bug: - Go to “Master Production schedule” - Set the number of records on a page to 2 (so you will have several pages) - Hover over "replenish" button Problem: Traceback is triggered: “Cannot read properties of null (reading 'getElementsByClassName')” When the mouse pointer enter or leave, the main "REPLENSIH" button, it triggers an event that fetch elements of the rows based on a specific class attribute: https://github.com/odoo/enterprise/blob/3b6aed1e5cab06720
Original PR description
Steps to reproduce the bug: - Go to “Master Production schedule” - Set the number of records on a page to 2 (so you will have several pages) - Hover over "replenish" button Problem: Traceback is…
Steps to reproduce the bug: - Go to “Master Production schedule” - Set the number of records on a page to 2 (so you will have several pages) - Hover over "replenish" button Problem: Traceback is triggered: “Cannot read properties of null (reading 'getElementsByClassName')” When the mouse pointer enter or leave, the main "REPLENSIH" button, it triggers an event that fetch elements of the rows based on a specific class attribute: https://github.com/odoo/enterprise/blob/3b6aed1e5cab06720c7f2f2120a9589b12a1dd34/mrp_mps/static/src/components/line.js#L163-L164 https://github.com/odoo/enterprise/blob/3b6aed1e5cab06720c7f2f2120a9589b12a1dd34/mrp_mps/static/src/components/line.js#L170-L171 As we have changed the number of records to 2, the other lines are no longer in view and will no longer refer to this specific class, so when we try to access them with `getElementsByClassName` it's throw a TypeError: cannot read properties of null. opw-3245457 Forward-Port-Of: odoo/enterprise#39567
On uninstall of sale_planning, planning slots linked to an SO line would just have their SO line set to null, resulting in a planning slot with neither start/end datetimes nor an SO line. Upon reinstalling sale_planning, setting up the `check_datetimes_set_or_plannable_slot` constraint would then fail, as the previously created slots would be in an invalid state. Cascade the deletion of SO lines into the planning slots, instead of just setting the FK to NULL. Forward-Port-Of: odoo/enterp
Original PR description
On uninstall of sale_planning, planning slots linked to an SO line would just have their SO line set to null, resulting in a planning slot with neither start/end datetimes nor an SO line. Upon reinstalling sale_planning, setting up the `check_datetimes_set_or_plannable_slot` constraint would then fail, as the previously created slots would be in an invalid state. Cascade the deletion of SO lines into the planning slots, instead of just setting the FK to NULL. Forward-Port-Of: odoo/enterprise#39682 Forward-Port-Of: odoo/enterprise#39614
When one doesn't set a due date for a document request the sent mail has this kind of message : (Planned on ) This commit fix that by removing the sentence when there is no due date. Task-3231376 Forward-Port-Of: odoo/enterprise#39386
Original PR description
When one doesn't set a due date for a document request the sent mail has this kind of message : (Planned on ) This commit fix that by removing the sentence when there is no due date. Task-3231376 Forward-Port-Of: odoo/enterprise#39386
Before this commit, one couldn't log out when on the portal share page, this was due to the missing of bootstrap assets such ass dropdown.js and popper.js One couldn't upload a document with a request a file shared page. Task-3231376 Forward-Port-Of: odoo/enterprise#38238
Original PR description
Before this commit, one couldn't log out when on the portal share page, this was due to the missing of bootstrap assets such ass dropdown.js and popper.js One couldn't upload a document with a request a file shared page. Task-3231376 Forward-Port-Of: odoo/enterprise#38238
The credit limit information and credit limit warning in the PoS were displaying when the credit limit was not active in the global settings and when the credit limit was 0 (usually meaning infinite in other places in Odoo). This was confusing or abnormal. Now the credit limit is displaying if the credit limit global setting is active AND the partner credit limit is bigger than 0 AND the partner overdue its credit limit. Forward-Port-Of: odoo/enterprise#39345
Original PR description
The credit limit information and credit limit warning in the PoS were displaying when the credit limit was not active in the global settings and when the credit limit was 0 (usually meaning infinite in other places in Odoo). This was confusing or abnormal. Now the credit limit is displaying if the credit limit global setting is active AND the partner credit limit is bigger than 0 AND the partner overdue its credit limit. Forward-Port-Of: odoo/enterprise#39345
This fixes the EDI format compatibility validation on journals in other locations. Also pass the journal country code validation to the journal EC types implementation validation, copying the way other locations do. Forward-Port-Of: odoo/enterprise#37933
Original PR description
This fixes the EDI format compatibility validation on journals in other locations. Also pass the journal country code validation to the journal EC types implementation validation, copying the way other locations do. Forward-Port-Of: odoo/enterprise#37933
To reproduce ============ - on any app that has a notebook - on studio make one of the pages invisible - try to make this page visible again (impossible) Problem ======= When setting the page invisible the checkbox is not checked, so clicking on it again will trigger action to make the page invisible. The issue comes from the fact that the `checked` value of this checkbox is binded to `widget.state.attrs.invisible` but from 16, the invisible modifier is not included in `attrs` directly
Original PR description
To reproduce ============ - on any app that has a notebook - on studio make one of the pages invisible - try to make this page visible again (impossible) Problem ======= When setting the page invisible the checkbox is not checked, so clicking on it again will trigger action to make the page invisible. The issue comes from the fact that the `checked` value of this checkbox is binded to `widget.state.attrs.invisible` but from 16, the invisible modifier is not included in `attrs` directly but in `attrs.modifiers`. Solution ======== use `widget.state.attrs.modifiers.invisible` opw-3233079 Forward-Port-Of: odoo/enterprise#39711 Forward-Port-Of: odoo/enterprise#38489
Purpose: - Currently, when unfolding an article in the sidebar, a "404 not found" message is added under the row of the unfolded article if this article is not accessible by the user anymore or if it has been deleted. Now, an AccessError will be shown to the user, so that he knows why he cannot unfold the article, and the article will be removed from the sidebar. Task-3266638 Forward-Port-Of: odoo/enterprise#39454
Original PR description
Purpose: - Currently, when unfolding an article in the sidebar, a "404 not found" message is added under the row of the unfolded article if this article is not accessible by the user anymore or if it has been deleted. Now, an AccessError will be shown to the user, so that he knows why he cannot unfold the article, and the article will be removed from the sidebar. Task-3266638 Forward-Port-Of: odoo/enterprise#39454
Add a `file -> Download as JSON` top menu to easily download the json content for manual edition some users may require. Forward-Port-Of: odoo/enterprise#39536 Forward-Port-Of: odoo/enterprise#38956
Original PR description
Add a `file -> Download as JSON` top menu to easily download the json content for manual edition some users may require. Forward-Port-Of: odoo/enterprise#39536 Forward-Port-Of: odoo/enterprise#38956
Have a button in a form view, with studio_approval=True on it to make sure the action won't be executed if the user doesn't have the right to do it. Create a new record, and click on that button. Before this commit, the call to check the approvals was passed without a resId, which did not crash the first time, but the return value was wrong as the record was not yet created. After this commit, we make sure we save the record before checking the approvals and before executing the wanted
Original PR description
Have a button in a form view, with studio_approval=True on it to make sure the action won't be executed if the user doesn't have the right to do it. Create a new record, and click on that button. Before this commit, the call to check the approvals was passed without a resId, which did not crash the first time, but the return value was wrong as the record was not yet created. After this commit, we make sure we save the record before checking the approvals and before executing the wanted action. opw-3254791 Forward-Port-Of: odoo/enterprise#39282
steps: helpdesk > configuration > stages > select any stage cause: text and the kanban label were not properly aligned issue: ps-0 was not giving space between the text and the kanban label fix: improved it with ps-2 to get space between the text and the kanban label task-3141892 Forward-Port-Of: odoo/enterprise#39554 Forward-Port-Of: odoo/enterprise#36041
Original PR description
steps: helpdesk > configuration > stages > select any stage cause: text and the kanban label were not properly aligned issue: ps-0 was not giving space between the text and the kanban label fix: improved it with ps-2 to get space between the text and the kanban label task-3141892 Forward-Port-Of: odoo/enterprise#39554 Forward-Port-Of: odoo/enterprise#36041