Thursday, December 28, 2023
6 changes · master
Enhancements to existing features
Indian invoicing now stores HSN compliance values on each invoice instead of only relying on product records. This makes invoice lines and related e-invoicing or e-waybill reports more accurate and easier to review for compliance.
Original PR description
Before this commit ================== HSN Codes are mapped to Product and same Carried to the various reporting level. After this commit ================= HSN Codes are stored at invoice level and displayed in invoice lines Related upgrade PR: https://github.com/odoo/upgrade/pull/5418 task- 3410236
Project updates now produce clearer reports with key details such as status, progress, milestones, profitability, and budget information in one place. The printed/PDF layout is also cleaner and easier to read, helping teams and customers follow project health without digging through side panels or chatter.
Original PR description
Purpose of this commit to improve the generic usage of project app So in this commit done the following changes: ----------------- - project.update description > milestones section: - indicate…
Purpose of this commit to improve the generic usage of project app
So in this commit done the following changes:
-----------------
- project.update description > milestones section:
- indicate "milestone name (SOL - x%) (due mm/dd/yyyy)
- project.update: add a 'project updates' report as follows:
- name of the update
- small table with the date, author, progress, status
- content of the description
- project.update description:
- add the 'profitability' table from the right side panel to the description
- add a new 'budget' section
- move the 'budget' sentance under that section
- and add the same 'budget' table as the one in the right side panel
- same visibility conditions apply
- grey every other lines of the tables to ease the reading
project: improve project update pdf report layout
--------------
task-2956738Users working with Indian invoicing now receive a warning when an invoice sequence is too long or contains unsupported special characters. This helps prevent invalid invoice numbering before documents are finalized, reducing compliance and correction issues.
Original PR description
Before this PR, users could enter more than 16 characters or any special characters for an invoice sequence. After this PR, if a user enters an invalid sequence format, they will receive a warning message. **Task**-3645816
Project updates now include budget information in their descriptions, making it easier for users to understand budget status alongside project progress. This improves visibility for teams using timesheets and budgets without requiring extra navigation.
Original PR description
Purpose of this commit to improve the generic usage of sale_timesheet_account_budget app So in this commit done the following changes: - add budget content in 'project.update' description. task-2956738
Quality Points can now only assign a Responsible person who belongs to the same company, is an internal user, and has the required Quality module access. This helps prevent incorrect assignments to people who cannot access or act on the Quality Point, improving operational accuracy and consistency across views.
Original PR description
Currently, it's possible to assign all users as Responsible to a Quality Point, even users having no access to that company, or external users. This restricts the Responsible user to be: - In the same company as the Quality Point - An internal user - At least a 'User' of the Quality module Added the widget in form view to keep it consistent with the other views.
Resolved issues and error corrections
This fixes an issue where newly added related records, such as project subtasks, could open before their inherited details were saved. Users now see complete and consistent information when clicking View across affected screens.
Original PR description
Steps: This is a generic issue occurring in different modules. Here, I mention one of the flow in the Project module. Open the Project module. Open any project. Add a subtask. Without manually saving…
Steps: This is a generic issue occurring in different modules. Here, I mention one of the flow in the Project module. Open the Project module. Open any project. Add a subtask. Without manually saving the subtask beforehand, click on 'View'. Form view of sub-task opens that doesn't have any of the fields it should inherit from its parent task. Go back to the parent task using the breadcrumbs. Click on 'View' again. Now, the sub-task has all of its fields set as it should. Issue: After clicking on 'View', the form view of the sub-task opens, but it doesn't have any of the fields it should inherit from its parent task. Cause: On clicking 'View', the switchToForm action is called, and this action doesn't save records before switching to the form view. Also, it should load that record into the Parent task after saving. In other modules, when clicking on 'View', the openRecord action is called, which is also not saving data. Fix: Records should be saved when the action is called on clicking 'View'. For the project module, when the action is called, after saving the record, it should also load records in the parent task. task-3508251