Saturday, June 1, 2024
10 changes · master
Enhancements to existing features
When a future task is cancelled, its planned date is now cleared so it no longer influences user scheduling. This helps keep workload planning accurate by excluding work that will not be performed.
Original PR description
We expect cancelled future tasks to have no impact on the scheduling of users as they are tasks that we are not going to work on. task-3853235
Resolved issues and error corrections
Fixed an issue where new filters on aged partner balance reports did not refresh properly and could cause an error. This helps users apply report filters reliably without interruptions.
Original PR description
During this commit https://github.com/odoo/enterprise/commit/a7a22def92832d1201eb8424ec45710eb9000a2c We introduced new filters on the aged partner reports but it didn't comply with this commit https://github.com/odoo/enterprise/commit/748f529abbdbd35f7249fa60698d1e2203b06bb2 that made the dirtyFilter reactive. This caused the filter to not update itself and caused a traceback. task-3909057
Features or functions removed from Odoo
This change removes unused code from the Belgian VAT report export process. It helps keep the reporting module simpler and easier to maintain without changing business functionality.
Original PR description
The aim of this commit is removing dead code that should be deleted in master. no task id
Miscellaneous changes
It makes no sense to have this test working with external since we're not checking CFDI content. Plus we fix the date to avoid errors. task-no Forward-Port-Of: odoo/enterprise#63572
Original PR description
It makes no sense to have this test working with external since we're not checking CFDI content. Plus we fix the date to avoid errors. task-no Forward-Port-Of: odoo/enterprise#63572
When a purchase order was matched and imported by the OCR, it wasn't working properly, the data imported was overwritten with the detected fields of the OCR. This happened because, in the implementation before this commit, a flag `force_write` was used to indicate that the data should be overwritten, but this implied that the data imported from the PO was also overwritten. In this new implementation, the content of the invoice is first reset and then the logic to fill in the invoice with t
Original PR description
When a purchase order was matched and imported by the OCR, it wasn't working properly, the data imported was overwritten with the detected fields of the OCR. This happened because, in the implementation before this commit, a flag `force_write` was used to indicate that the data should be overwritten, but this implied that the data imported from the PO was also overwritten. In this new implementation, the content of the invoice is first reset and then the logic to fill in the invoice with the OCR data and/or purchase order is applied. Task: [#3834665](https://www.odoo.com/odoo/project.task/3834665?cids=1) Forward-Port-Of: odoo/enterprise#63510 Forward-Port-Of: odoo/enterprise#63290
**Steps to reproduce:** - Install Timesheet module - Check the grid view and make sure you have odd number of rows - Scroll horizontally and see the row of the column total **Current behavior before PR:** The values of the column total still visible when scrolling horizontally while it should be hidden. This is happening because in this commit https://github.com/odoo/enterprise/pull/48406/commits/ec733d78385dee23ca2e338f49c089030b83f4c4 the bg-100 has been removed so when the row of
Original PR description
**Steps to reproduce:** - Install Timesheet module - Check the grid view and make sure you have odd number of rows - Scroll horizontally and see the row of the column total **Current behavior before PR:** The values of the column total still visible when scrolling horizontally while it should be hidden. This is happening because in this commit https://github.com/odoo/enterprise/pull/48406/commits/ec733d78385dee23ca2e338f49c089030b83f4c4 the bg-100 has been removed so when the row of the column total is not in even position its cell in the first column won't have a bg in its class so when values get behind this cell it will still be visible and will overlay. **Desired behavior after PR is merged:** We added the bg-100 once again so when the row is not in even position it will still hide the values when scrolling horizontally opw-3943960 Forward-Port-Of: odoo/enterprise#63446
Planning : fix the spacing issue in slot conflict warning -------------- Steps to reproduce: - Open planning - Click on a slot which has already been allocated and add select both role and project - Open the first task in the slot to get the slot conflict warning text. Issue: - There is a large gap between Slot timings and percentage. Cause: - The whole warning is in a d-grid where conflict slot timings are one and other total hours role and project are another part of both l
Original PR description
Planning : fix the spacing issue in slot conflict warning -------------- Steps to reproduce: - Open planning - Click on a slot which has already been allocated and add select both role and project -…
Planning : fix the spacing issue in slot conflict warning
--------------
Steps to reproduce:
- Open planning
- Click on a slot which has already been allocated and add select both role and project
- Open the first task in the slot to get the slot conflict warning text.
Issue:
- There is a large gap between Slot timings and percentage.
Cause:
- The whole warning is in a d-grid where conflict slot timings are one and other total hours role and project are another part of both length 1fr.
- So whenever there is project name and role_id it makes the both of same length 1fr which adds the gap in true sense.
Selection:
- Using auto for the first part makes sure that the timing section does have fixed length.
- Also the timing section of the grid is the same unlike the the details section
Industry : fix creation of non-fsm task in fsm
------------
Steps to reproduce:
- Open Field Service
- Create a task so that a conflict b/w task is created
- Click on the conflicting task and click on edit
- In the form a conflict warning is shown
- Click on 'Check It Out'
- In the view opened view click on any empty slot
Issues:
- The issue is that in the opened form Field Service is not selected as default
project the task is set to 'Private'
Cause:
- Missing context causing this
Solution:
- Passing a context in the action window solves the issue.
task:3850839
Forward-Port-Of: odoo/enterprise#60602This commit hides the unused "rating_last_text" field from the list view of tickets, preventing a duplicate rating. Linked PR: https://github.com/odoo/enterprise/pull/52371 task-3869775 Forward-Port-Of: odoo/enterprise#60761
Original PR description
This commit hides the unused "rating_last_text" field from the list view of tickets, preventing a duplicate rating. Linked PR: https://github.com/odoo/enterprise/pull/52371 task-3869775 Forward-Port-Of: odoo/enterprise#60761
Create a new journal entry Post it Reset to draft Delete the name Go to General Ledger Export PDF Error TypeError: object of type 'NoneType' has no len() This occurs because when the name field is blanked, it is set to False opw-3925088 Forward-Port-Of: odoo/enterprise#63161
Original PR description
Create a new journal entry Post it Reset to draft Delete the name Go to General Ledger Export PDF Error TypeError: object of type 'NoneType' has no len() This occurs because when the name field is blanked, it is set to False opw-3925088 Forward-Port-Of: odoo/enterprise#63161
This commit fixes an issue with the editor toolbar in mobile mode. The toolbar overlaps some elements inside a knowledge article, e.g. separators and embedded views. This is because in mobile the toolbar has a z-index auto which means that it has the same z-index as the editor which can be lower than some elements with an index set. Before it wasn't an issue as the toolbar wasn't sticky so it disappeared when you scrolled on mobile. But the `position: sticky;` forces us to take the z-index int
Original PR description
This commit fixes an issue with the editor toolbar in mobile mode. The toolbar overlaps some elements inside a knowledge article, e.g. separators and embedded views. This is because in mobile the toolbar has a z-index auto which means that it has the same z-index as the editor which can be lower than some elements with an index set. Before it wasn't an issue as the toolbar wasn't sticky so it disappeared when you scrolled on mobile. But the `position: sticky;` forces us to take the z-index into account. To fix this, the css rule is removed so that the toolbar uses its original index which places it back on top of the other blocks. task-3939911 Forward-Port-Of: odoo/enterprise#62975