Friday, March 26, 2021
5 changes
New functionality added to Odoo
Adds tools to classify vendors by 1099 type and export summarized vendor journal entries for a chosen date range. This helps businesses prepare the required CSV data for 1099 e-filing through third-party services, reducing manual reporting work.
Original PR description
This allows vendors to be categorized with a 1099 type. A wizard allows users to export and sum journal items belonging to this vendor in a date range. The generated CSV contains all the information necessary to e-file through a 3rd party service. Task ID: 2222281
Enhancements to existing features
Projects now support tasks by default, while field service projects keep their specific task behavior. This reduces confusion around subtasks appearing in project and field service views and aligns the enterprise apps with the wider project management update.
Original PR description
This commit follows the changes introduced by task-2388034. With this commit we want to remove the definition of group project subtask. Tasks are now available by default on each project expect on fsm project task-2388034 : sub-task of : task-2379043 See : https://github.com/odoo/odoo/pull/62577 PR upgrade: odoo/upgrade#1984
Resolved issues and error corrections
Users now receive a clear error message when the system cannot find the required numbering sequence for new records. This prevents confusing record names and helps administrators quickly identify and fix missing sequence setup across affected business flows.
Original PR description
Sales orders that include campaign tracking details now pass those details to the subscriptions they create. This helps teams connect subscription revenue back to the marketing campaigns or links that generated the original sale.
Original PR description
Propagate UTM from SO to subscriptions taskid: 2457461
Helpdesk teams can now automatically move inactive tickets to a closing stage after a configurable number of days. This reduces manual follow-up work for support agents and helps keep ticket queues cleaner when customers stop responding.
Original PR description
Purpose of the task is, If often happens that a customer stops answering to his ticket when he feels that he was provided a good solution to this problem. In such case, the support agent has to…
Purpose of the task is, If often happens that a customer stops answering to his ticket when he feels that he was provided a good solution to this problem. In such case, the support agent has to manually scan of all the tickets he is in charge of, chase the customer and move the ticket to a closing stage. Support agents would save a lot of time if this process was automated.
so in this commit, added the following setting under helpdesk team:
- name: Automatic Closing
- description: Close inactive tickets automatically
- 'Inactivity period _____ days' field with default value = 7 days
- 'In Stages' m2m, not required; should take all the stages of the
team into account if left empty, and be restricted to the selected stages if set
- 'Move to Stage' m2o required
when a ticket reaches the 'inactivity period' defined (without interruption) in
one of the selected 'in stages' stages, move the ticket automatically to the
'move to stage' stage
- also rename the 'ticket closing' feature into 'Ticket Self-closing'
TaskID: 2466235Purpose: Display proper error message when sequence not found. Specification: raise error instead of returning FALSE when sequence not found Task-1974068