Saturday, March 28, 2026
4 changes · saas-19.2
New functionality added to Odoo
This update incorporates changes to India's tax regulations as outlined in the Income Tax Bill 2025, specifically regarding TDS and TCS. It adds new tax sections and groups to ensure compliance with the updated IT Act, improving the system's accuracy for Indian businesses.
Original PR description
The Income Tax Bill 2025 introduces TDS and TCS provisions in a more structured way compared to the existing Income-tax Act 1961, with the addition of new sections and taxes. This commit adds new sections and corresponding taxes for sections 392, 393, and 394, along with their respective reports. It also introduces new TDS and TCS tax groups for these taxes to differentiate them from the existing ones. The old taxes are deactivated as they are no longer applicable. task-6035844 Forward-Port-Of: odoo/odoo#256521 Forward-Port-Of: odoo/odoo#256102
Enhancements to existing features
This update simplifies the process for planning managers to finalize shifts. Now, marking a shift as 'completed' directly triggers the generation of related documents like timesheets and sales orders, without requiring manual steps. A warning is displayed to confirm the action, ensuring accuracy and efficiency.
Original PR description
Use case: The day is finished and I want to record all the shifts that I worked on that day. But without going through the entire flow by using the buttons (signing-in, marking the shift as completed, etc). Instead, we allow the user (planning manager) to directly mark the shift as in draft, progress, scheduled or completed by using the status bar of the shift state. When changing the state to any other states as completed, we only change the state but do nothing else. When changing the state to completed, we proceed with the generation of the timesheets, the sale rrder, stock moves, etc, except that we don't change the end date of the shift or redirect the user to the portal after editing the state. Also, we warn the user before changing the state to completed, to make sure he wants to perform that change and trigger the related actions. task-5966615 version-19.2
Resolved issues and error corrections
This update enhances the Project Budget reporting experience by clarifying key metrics, adding a progress graph, and streamlining the user interface. It also resolves an issue where billable types were incorrectly classified when installing the sale_timesheet module, ensuring accurate tracking of project costs.
Original PR description
This task provides corrections and follow‑up work related to PR IMP #104599. ## Expected Behavior After This Commit 1. Renamed the stat buttons in the Project form view to make their purpose clearer.…
This task provides corrections and follow‑up work related to PR IMP #104599. ## Expected Behavior After This Commit 1. Renamed the stat buttons in the Project form view to make their purpose clearer. 2. Corrected breadcrumb generation when accessing the Project form view from the top menu. 3. Adjusted the project update form view to remove excessive padding. 4. Added a graph to the project update view to visualize project progress over time. 5. Updated filters in the margin search view. 6. Improved billable type labels for better user clarity. 7. Ensured billable types are updated correctly when sale_timesheet is installed. 8. Added navigation from analytic lines to their parent record in the margin list view. 9. Added three colors (gray, green, red) to the Milestone stat button. 10. Improved the kanban view of projected margins. ## Additions ### Point 2 — Breadcrumb Fix When navigating from the top menu to the Project Overview, breadcrumbs were not generated correctly. To resolve this, a multi‑step flow was implemented: - Clicking the "Overview" button triggers the action `project_embedded_action_project_overview`. - This action calls the Python method `action_open_project_form`, which then triggers the client action `project_top_menu_overview`. - The client action uses the `doAction` service to open the Project form view. This approach is required because: - Breadcrumbs are generated correctly only when `doAction` is executed inside a client action. - The "Overview" button cannot directly trigger a client action, making the Python intermediary necessary. ### Point 7 — Billable Type Synchronization The `sale_project` module defines the `billable_type` field on `account_analytic_line`, including the generic types *Other Revenues* and *Other Costs*. The `hr_timesheet` module adds additional, more specific billable types. A problem occurs when: - `sale_project` is installed first, causing analytic lines that should belong to `hr_timesheet` billable types to be incorrectly classified under *Other Revenues* or *Other Costs*. - When `hr_timesheet` is installed afterward, these analytic lines are not automatically updated. This fix ensures that potentially misclassified analytic lines are corrected when both `hr_timesheet` and `sale_project` are installed. ## Task : task-[5955934](https://www.odoo.com/odoo/project/4105/tasks/5955934)
This update enhances the Project Budget module by clarifying navigation, adding a progress graph, and resolving issues with billable type synchronization when the sale_timesheet module is installed. It ensures accurate reporting and a better user experience for managing project finances.
Original PR description
This task provides corrections and follow‑up work related to PR : IMP #236971 . ## Expected Behavior After This Commit 1. Renamed the stat buttons in the Project form view to make their purpose…
This task provides corrections and follow‑up work related to PR : IMP #236971 . ## Expected Behavior After This Commit 1. Renamed the stat buttons in the Project form view to make their purpose clearer. 2. Corrected breadcrumb generation when accessing the Project form view from the top menu. 3. Adjusted the project update form view to remove excessive padding. 4. Added a graph to the project update view to visualize project progress over time. 5. Updated filters in the margin search view. 6. Improved billable type labels for better user clarity. 7. Ensured billable types are updated correctly when sale_timesheet is installed. 8. Added navigation from analytic lines to their parent record in the margin list view. 9. Added three colors (gray, green, red) to the Milestone stat button. 10. Improved the kanban view of projected margins. ## Additions ### Point 2 — Breadcrumb Fix When navigating from the top menu to the Project Overview, breadcrumbs were not generated correctly. To resolve this, a multi‑step flow was implemented: - Clicking the "Overview" button triggers the action `project_embedded_action_project_overview`. - This action calls the Python method `action_open_project_form`, which then triggers the client action `project_top_menu_overview`. - The client action uses the `doAction` service to open the Project form view. This approach is required because: - Breadcrumbs are generated correctly only when `doAction` is executed inside a client action. - The "Overview" button cannot directly trigger a client action, making the Python intermediary necessary. ### Point 7 — Billable Type Synchronization The `sale_project` module defines the `billable_type` field on `account_analytic_line`, including the generic types *Other Revenues* and *Other Costs*. The `hr_timesheet` module adds additional, more specific billable types. A problem occurs when: - `sale_project` is installed first, causing analytic lines that should belong to `hr_timesheet` billable types to be incorrectly classified under *Other Revenues* or *Other Costs*. - When `hr_timesheet` is installed afterward, these analytic lines are not automatically updated. This fix ensures that potentially misclassified analytic lines are corrected when both `hr_timesheet` and `sale_project` are installed. ## Task task-[5955934](https://www.odoo.com/odoo/project/4105/tasks/5955934) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr