Daily updates from Odoo
Navigate
Branch
Monday, November 25, 2019
49 changes
Security fixes and vulnerability patches
This update reduces security exposure around payment providers by limiting access to sensitive configuration fields and tightening internal payment processing methods. It helps prevent unauthorized changes or misuse of payment provider accounts while also slightly improving payment form rendering performance.
Original PR description
Reduce the attack surface on payment providers by: - enforcing private methods everywhere a public one is not required for the modules to work - add group security on sensitive fields - avoid invisible sudoification of records through method calls task-1969945 Enterprise PR odoo/enterprise#4744
New functionality added to Odoo
Mobile users can now add a new Kanban column directly from a dedicated “Add Column” tab. This makes board management easier on phones and keeps users in the right place after creating or cancelling a column.
Original PR description
Task: https://www.odoo.com/web?debug=1#id=1893137&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.39bed8937b446b5c076185288f5f6e1b -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Sales users can now enable a product grid configurator to choose multiple product variants in a single flow. This helps teams handle products with many variants more efficiently and reduces repetitive order entry work.
Original PR description
Enterprise PR: odoo/enterprise#4605
A new product variant grid lets users choose quantities for several product variants in one place instead of adding each variant separately. This speeds up sales order entry for products with many combinations, such as sizes, colors, or other attributes.
Original PR description
Community PR: odoo/odoo#34200
The currency rate live update feature now supports Chile's SBIF service, allowing businesses to automatically retrieve Chilean exchange rates when they provide an SBIF API token. This reduces manual currency maintenance for companies operating in Chile and keeps financial rates more current.
Original PR description
This adds sbif connection to "currency_rate_live" module. It requires an API Token. It can be obtained from SBIF site.
Enhancements to existing features
Odoo now uses the same fiscal position lookup method across accounting, sales, purchasing, point of sale, repairs, and website sales. This improves consistency in how taxes and accounts are selected for customers and vendors, reducing the risk of mismatched fiscal treatment across different business flows.
Original PR description
Always use get_fiscal_position and not property_account_position_id in Odoo codebase And some cleanups in account: * map_tax supports empty self * get_fiscal_position returns a fiscal position recordset, not an id/False anymore -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Manufacturing orders can no longer be created through the calendar’s quick-create shortcut. This avoids confusing entries where the typed summary is replaced by the system-generated order number, leading users toward the full creation flow instead.
Original PR description
Task-https://www.odoo.com/web?#id=2052536&action=333&active_id=1519&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.a0298c6e2160bc653a9c533b108f364a -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Odoo now handles missing or deleted default activity types more gracefully by falling back to a standard activity instead of raising errors. It also prevents deletion of activity types that are still needed by HR plans or automated server actions, reducing disruptions in workflows that rely on scheduled activities.
Original PR description
**Update of https://github.com/odoo/odoo/pull/32446** If a user deletes one of the default activity types of odoo, a bunch of ref to the xmlid of the activity type may cause errors. To allow more…
**Update of https://github.com/odoo/odoo/pull/32446**
If a user deletes one of the default activity types of odoo, a bunch of ref to the xmlid of the activity type may cause errors.
To allow more flexibility, this a fallback mechanism is implemented in mail.activity.mixin s.t. when calling activity_schedule(xmlid, ...), if the given xmlid is not found, default_activity_type() specifies the default activity (and can be overridden in classes using the activity mixin).
```python
def _default_activity_type(self):
"""Define a default fallback activity type when xml id not found
only used in in activity_schedule() for now.
"""
try:
return self.env.ref('mail.mail_activity_data_todo')
except Exception:
return False
```
- Prevent deletion of activity type (hr.plan and ir.actions.server)
- Fallback on default activity type if xmlid ref not found in activity_schedule
- Correct calls to activity_schedule and replace some create calls by activity_schedule
Task ID : 1961156
Enterprise PR: https://github.com/odoo/enterprise/pull/6238
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prViews opened from the Product Margin report no longer show unnecessary Create and Edit buttons. This reduces confusion and helps users focus on reviewing margin information rather than making changes from report drill-downs.
Original PR description
Description of the issue/feature this PR addresses: Fixes https://github.com/odoo/odoo/issues/39069 Current behavior before PR: Desired behavior after PR is merged: Create and Edit Buttons are not needed on views being opened from Product Margin report -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The French chart of accounts now includes tags that classify accounts into operating, financing, investing, and extraordinary activities. This improves the accuracy and usability of cash flow and financial reporting for French accounting users.
Original PR description
Description of the issue/feature this PR addresses: added tag in accounts for 'compte de résultat' financial report Task: https://www.odoo.com/web#id=1973937&action=327&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.67e8ba0a372f7f82bba0680aa9067602 Current behavior before PR: Desired behavior after PR is merged:
The Norwegian localization now uses the newer RF-0002 format for financial tax reporting. This helps businesses in Norway align their Odoo reports with updated reporting requirements and reduces manual adjustments during compliance processes.
Original PR description
Task : https://www.odoo.com/web#id=1969011&action=327&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.27eb04e13e8e3e3e624b0d80e13acb2a -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Point of Sale sessions now keep and show the actual cash closing difference after validation. This helps store managers review the real end-of-session cash variance later instead of seeing it reset to zero.
Original PR description
Description of the issue/feature this PR addresses: We want to see the real ending cash balance in the pos session form when the session is closed. Current behavior before PR: When we close the pos session, once you click "validate closing & post entries", the difference is transfered to transaction and the difference set back to zero. We don't store the real diff before the calculation and once the session is closed we always see a difference of 0. Desired behavior after PR is merged: When the pos session is closed, we now display the correct ending difference before the validation. Task-Id: 2032173 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Mobile users can now add new columns directly from Kanban views, making board management possible without switching to desktop. This improves usability for teams managing workflows on phones or tablets.
Original PR description
Task:https://www.odoo.com/web#id=1893137&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.39bed8937b446b5c076185288f5f6e1b -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Time off types can now use different approval paths for allocation requests and actual leave requests. This lets businesses route allocation approvals to the right manager or officer without changing who approves employees taking time off.
Original PR description
Purpose ======= We want to allow different approvals for allocations and leaves of a same type. e.g. In case of compensation days, a manager would approve the allocation request, but would later not…
Purpose ======= We want to allow different approvals for allocations and leaves of a same type. e.g. In case of compensation days, a manager would approve the allocation request, but would later not approve leave requests. Specification ============= Allocation modes ---------------- No change here except renames. 1. No limit (employee doesn't need an allocation to request a leave) 2. Allow employee requests 3. Fixed by Time Off Officer Allocation approval ------------------- A radio field to choose the approval mechanism appears if the employee is allowed to request an allocation. The following approval modes are possible: 1. Time Off Officer 2. Employee's Time Off Manager (leave_responsible_id) 3. Employee's Time Off Manager and Time Off Officer These options are the same as leave approval options (except the missing "No Validation"). If option 1 or 2 is selected, a o2m field should allow to select which Time Off Officer is responsible for approving those allocations. Allocation approval policy is the same as the leave approval policy. Task id: 1936742 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Mobile users can now add new columns directly in kanban views using a plus button in the tab bar. This improves setup flows such as creating project stages, especially when a new project has no columns yet.
Original PR description
On mobile, there was no way to create a new column in the kanban view. This was specifically annoying in the Project app (the user was able to create the project but couldn't set its stages). This commit enables this feature by adding a `+` icon at the end of the tabs. This button opens a quick-create column widget. If there is no existing column (for example in a newly created project), this quick-create column widget is opened by default. Finally, this commit improves the processing needed for the swipe animation between the columns. Task ID: 1893137
Survey management has been streamlined to better show quiz scores and the last page reached by respondents. The underlying survey logic was also cleaned up to reduce unnecessary background calls, improving maintainability and day-to-day usability.
This pull request updates the Survey app, touching response handling, survey page behavior, submission logic, and related page assets. The available title and commit message do not describe the business goal, so the change appears to be a small survey-related adjustment rather than a broad functional rollout.
This update standardizes how automated activity reminders are created across several business apps, making them easier to manage and clean up. It also improves default activity type selection so users get more consistent follow-up behavior and reduces the risk of important activity types being deleted incorrectly.
Original PR description
**Update of https://github.com/odoo/enterprise/pull/4032** - hr.approval : default activity_type - Fixes/Clean on activity creation in some modules Task ID : 1961156 Community PR: https://github.com/odoo/odoo/pull/39013 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update makes fiscal position selection and tax mapping more consistent across related sales, marketplace, subscription, and inter-company workflows. Businesses should see fewer tax mismatches when orders or subscriptions are created through different channels.
The Web Studio “add chatter” option now looks better aligned and responds more quickly when users interact with it. This creates a smoother, more polished editing experience without changing business workflows.
Original PR description
task - https://www.odoo.com/web#id=2094895&action=327&model=project.task&view_type=form&menu_id=4720 pad - https://pad.odoo.com/p/r.9e4262257b785c8623839c8ffa87bfb3 - The label 'add chatter' widget was not vertically centered. By this commit the design issue has been improved. - Also the transition effect speed has been increased for better user experience.
The payroll account test setup for Belgian localization was adjusted so it runs after installation, avoiding failures caused by company setup data not being available early enough. This improves test reliability without changing business payroll behavior for users.
Original PR description
Rule parameter tests are tagged as post install because when creating a company, the required field `extract_show_ocr_option_selection` has a column in database (with a non null constraint) but the field is not yet loaded in the registry. Therefore, the default value is not used when inserting in the database and the contraint fails.
The French financial report for the profit and loss statement now better classifies accounts using activity tags such as operating, financing, investing, and extraordinary activities. This makes the report clearer and more useful for reviewing business performance in France.
Original PR description
Improve financial report "compte de résultat" Task: https://www.odoo.com/web#id=1973937&action=327&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.67e8ba0a372f7f82bba0680aa9067602
Resolved issues and error corrections
Out-of-office messages now show the true return date when an employee has back-to-back leave periods, even if they use different leave types or the leave spans a weekend. This prevents colleagues from expecting someone back too early and improves planning around employee availability.
Original PR description
Description of the issue/feature this PR addresses: Task: https://www.odoo.com/web#id=2002525&action=327&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.8af0c15014b1a6004e4f2456cca069ee Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This change fixes an internal test that could fail when Odoo runs with stricter logging settings. It helps keep automated checks stable across different server configurations without changing business features or user workflows.
The accounting menu label now uses the same “Refunds” wording as other menus. This reduces confusion for users by keeping terminology consistent across the system.
Original PR description
Description of the issue/feature this PR addresses: Fix wording to be like other menus Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The LDAP login integration now handles names and other values containing non-English or accented characters correctly. This prevents errors during later processing and improves reliability for companies using LDAP directories with international user data.
Original PR description
Non-ascii characters in LDAP don't cause a python unicode string in returned ldap entries, this commit fixes this. Before this commit, further string operations on ldap values with non-ascii characters fail. Cherry-pick of #12745 by @hbrunn
Odoo now validates standard views even when they have been marked as protected from updates in the database. This helps catch broken screen layouts during module upgrades instead of letting invalid views remain unnoticed.
Original PR description
I tried to write a detailed yet understandable commit message. I failed. The point is that views set to `noupdate` in database were not validated. This is the case since OpenERP 8.0. They are now.
The map view now ignores drag, zoom, and hover actions when users interact with an alert message placed over the map. This prevents accidental map movement and makes the notice less alarming by showing it as an informational message.
Original PR description
Task : https://www.odoo.com/web?#id=%20&action=327&model=project.task&view_type=form&menu_id=4720 PAD : https://pad.odoo.com/p/openerp-project.task-E057WKI46W
Canceled customer invoices are now excluded from bank reconciliation suggestions. This prevents users from accidentally matching payments to voided invoices and keeps reconciliation results accurate.
Original PR description
Steps to reproduce the bug: - Let's consider customer P - Create two customer invoices C1 and C2 for P - Cancel C1 - Go to bank reconciliation - Create a statement with a line for P - Click on 'Reconcile' Bug: C1 was suggested to be reconciled opw:2120756
The barcode settings page now hides the default barcode nomenclature option unless debug mode is enabled. This reduces clutter and helps prevent regular users from changing an advanced configuration by mistake.
Original PR description
Task: https://www.odoo.com/web#id=2128359&action=327&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.2e11b3bdf793ef0a351394f97b30db91
Features or functions removed from Odoo
Cancelling a sales order in Odoo will no longer send a cancellation request to Amazon. This prevents accidental Amazon order cancellations during routine Odoo cleanup or resynchronization, while cancellations made on Amazon can still be reflected back in Odoo.
Original PR description
As of this commit, the cancellation of a sales order in Odoo no longer sends a cancellation notification to Amazon. It remains possible to synchronize the cancellation of an order from Amazon in Odoo.
The incentive is that synchronizing order cancellations from Odoo is:
* confusing: Apart from pickings, no data is ever sent to Amazon so users don't expect any action to take place after hitting 'cancel' on a sales order.
* dangerous: Cancelling a sales order is a required step to delete it, which may happen if a user wants to synchronize it again. If the related cron happens to run between the two steps, a cancellation notification will be sent to Amazon even if it wasn't intended.
task-2081442Code cleanup and technical improvements
The Survey app code and templates were reorganized to make future enhancements easier to build and maintain. This cleanup removes unused or duplicated code and separates survey pages, statistics, and management templates without intended changes for end users.
Original PR description
PURPOSE Purpose is to perform some cleaning in survey models: naming, ordering, dead code [0]. As new features are about to land in survey, notably live interactions [1] and new survey building [2] performing a pre cleaning is necessary [3]. SPECIFICATIONS This merge contains three commits doing * code move; * dead code removal; * templates split to ease understanding and reading; See sub commits for more details. LINKS [0] Related to Task ID 2144393 (surveys split / cleaning) [1] Task ID 1972640 (live interactions) [2] Task ID 2119587 (new frontend for building surveys) [3] Task ID 2061901 (survey models cleaning and preparation) PR #40623
The appraisal module’s sample survey data was cleaned up to better align with related updates. This is an internal housekeeping change that improves demo data quality without changing day-to-day user workflows.
Miscellaneous changes
A customer reported an issue when he tried to add a link on the blog covers of his blog. The link is displayed as text and it's added to all the covers.  According to SBU, the user should not do this. This commit prevents the user from adding a link on a blog cover. OPW-2119924 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#40783 Forward-Port-Of: odoo/odoo
Original PR description
A customer reported an issue when he tried to add a link on the blog covers of his blog. The link is displayed as text and it's added to all the covers.  According to SBU, the user should not do this. This commit prevents the user from adding a link on a blog cover. OPW-2119924 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#40783 Forward-Port-Of: odoo/odoo#40608
Description of the issue/feature this PR addresses: Task-ID: https://www.odoo.com/web?#id=2046885&action=327&model=project.task&view_type=form&menu_id=4720 Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#39009
Original PR description
Description of the issue/feature this PR addresses: Task-ID: https://www.odoo.com/web?#id=2046885&action=327&model=project.task&view_type=form&menu_id=4720 Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#39009
In the pivot view of report.pos.order that is a view mainly over pos.order, the "Count" measure is a little rubish giving more or less the number of different products in the grouped order lines. With this changeset, we have the field "Order" as measure that allow us to know the number of orders a grouping is corresponding to. opw-2127275 Forward-Port-Of: odoo/odoo#40723
Original PR description
In the pivot view of report.pos.order that is a view mainly over pos.order, the "Count" measure is a little rubish giving more or less the number of different products in the grouped order lines. With this changeset, we have the field "Order" as measure that allow us to know the number of orders a grouping is corresponding to. opw-2127275 Forward-Port-Of: odoo/odoo#40723
task: https://www.odoo.com/web#view_type=form&model=project.task&id=42243&active_id=42243&menu_id= pad: https://pad.odoo.com/p/r.0cc60a058652f804d7198ca71209f126 Forward-Port-Of: odoo/odoo#40776
Original PR description
task: https://www.odoo.com/web#view_type=form&model=project.task&id=42243&active_id=42243&menu_id= pad: https://pad.odoo.com/p/r.0cc60a058652f804d7198ca71209f126 Forward-Port-Of: odoo/odoo#40776
It was discussed previously from: - https://github.com/odoo/odoo/commit/b79d05fff0cacb4d99ebc1b60f44d8dab757b806 I quote @odony commit message: ``` Having it in INFO should be sufficient for its purpose, and will avoid impacting all CI builds done on a system that does not have the lib installed. For the record, this is not a hard requirement because the lib was not available in Debian stable packages at the time of release. It is only enabled on demand for those who want the fea
Original PR description
It was discussed previously from: - https://github.com/odoo/odoo/commit/b79d05fff0cacb4d99ebc1b60f44d8dab757b806 I quote @odony commit message: ``` Having it in INFO should be sufficient for its purpose, and will avoid impacting all CI builds done on a system that does not have the lib installed. For the record, this is not a hard requirement because the lib was not available in Debian stable packages at the time of release. It is only enabled on demand for those who want the feature and can install it manually. Fixes #22426 Closes #22459 ``` Forward-Port-Of: odoo/odoo#40738
This optimizes the prefetching of the other fields when you don't need the translated field. Forward-Port-Of: odoo/odoo#40706 Forward-Port-Of: odoo/odoo#40651
Original PR description
This optimizes the prefetching of the other fields when you don't need the translated field. Forward-Port-Of: odoo/odoo#40706 Forward-Port-Of: odoo/odoo#40651
The title says it all -_- Forward-Port-Of: odoo/odoo#39779 Forward-Port-Of: odoo/odoo#39699
Original PR description
The title says it all -_- Forward-Port-Of: odoo/odoo#39779 Forward-Port-Of: odoo/odoo#39699
Reproduce the issue - Install Projects - Create a project - Create a task with a deadline The deadline format is correct in the form view but not in the kanban view. Cause In the kanban view, there is some code applied on the `date_deadline` field to add a class when the deadline is near. As it uses a `span` with a `t-esc`, the only way to get the date is to do `record.date_deadline.raw_value` which return the raw value of the datetime
Original PR description
Reproduce the issue
- Install Projects
- Create a project
- Create a task with a deadline
The deadline format is correct in the form view but not in the
kanban view.
Cause
In the kanban view, there is some code applied on the `date_deadline`
field to add a class when the deadline is near.
As it uses a `span` with a `t-esc`, the only way to get the date
is to do `record.date_deadline.raw_value` which return the raw
value of the datetime object (a big string with all the infos).
This commit creates a char field for the formatted date and uses it
only for the display.
OPW-2122928
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#40599Description of the issue/feature this PR addresses: Because of the way odoo has to search with related fields in models without auto join, the performance in the sale order lines is diminishing. As the related and stored field salesman_id exists we can use it to make the search direct. Current behavior before PR: Bad performance Desired behavior after PR is merged: Good performance @Tecnativa TT20614 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.c
Original PR description
Description of the issue/feature this PR addresses: Because of the way odoo has to search with related fields in models without auto join, the performance in the sale order lines is diminishing. As the related and stored field salesman_id exists we can use it to make the search direct. Current behavior before PR: Bad performance Desired behavior after PR is merged: Good performance @Tecnativa TT20614 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#40565
…ss computation We are initializing over the limit to make sure we will compute it at least once. If the target goal is set to 0, we are facing a division by zero error when displaying the gamification goal just after initialization. Description of the issue/feature this PR addresses: opw-2127205 Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/o
Original PR description
…ss computation We are initializing over the limit to make sure we will compute it at least once. If the target goal is set to 0, we are facing a division by zero error when displaying the gamification goal just after initialization. Description of the issue/feature this PR addresses: opw-2127205 Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#40703 Forward-Port-Of: odoo/odoo#40666
Bug === In the feed view, if you click on an emoji (which is inside of a comment) there will be a traceback Fix === In the file ``stream_post_comments`` we bind ``click .o_mail_emoji`` to the emoji mixin method. This method will insert the emoji in the text. But, this event is also triggered if the user click on an emoji in read only mode. So, we need to change the target of the event (and to select only emojis which are in the dropdown menu). Task #2121750 Forward-Port-Of: odoo/en
Original PR description
Bug === In the feed view, if you click on an emoji (which is inside of a comment) there will be a traceback Fix === In the file ``stream_post_comments`` we bind ``click .o_mail_emoji`` to the emoji mixin method. This method will insert the emoji in the text. But, this event is also triggered if the user click on an emoji in read only mode. So, we need to change the target of the event (and to select only emojis which are in the dropdown menu). Task #2121750 Forward-Port-Of: odoo/enterprise#6626
When copying previous week, the bounds of the previous week must be computed in UTC. Ex: 18/11/2019 at 00:00:01 in UTC+1 is 17/11/2019 23:00:01 in UTC Let's consider the previous week with the following bounds [B1, B2] All the copied slots must include in the previous week meaning that: - All the start_datetime's slots >= B1 - All the end_datetime's slots <= B2 opw:2091602 Forward-Port-Of: odoo/enterprise#6760
Original PR description
When copying previous week, the bounds of the previous week must be computed in UTC. Ex: 18/11/2019 at 00:00:01 in UTC+1 is 17/11/2019 23:00:01 in UTC Let's consider the previous week with the following bounds [B1, B2] All the copied slots must include in the previous week meaning that: - All the start_datetime's slots >= B1 - All the end_datetime's slots <= B2 opw:2091602 Forward-Port-Of: odoo/enterprise#6760
Task : https://www.odoo.com/web?#id=2095236&action=327&model=project.task&view_type=form&menu_id=4720 Pad : https://pad.odoo.com/p/openerp-project.task-WK8XD1ME4G Forward-Port-Of: odoo/enterprise#6643
Original PR description
Task : https://www.odoo.com/web?#id=2095236&action=327&model=project.task&view_type=form&menu_id=4720 Pad : https://pad.odoo.com/p/openerp-project.task-WK8XD1ME4G Forward-Port-Of: odoo/enterprise#6643
Task: https://www.odoo.com/web#id=2126097&action=327&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.63737a7423deddbe92bb6b204c28c505 Forward-Port-Of: odoo/enterprise#6830
Original PR description
Task: https://www.odoo.com/web#id=2126097&action=327&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.63737a7423deddbe92bb6b204c28c505 Forward-Port-Of: odoo/enterprise#6830
PR linked to #40599 (community) As I removed the date_format, the FSM app crashed because it's using it. I added a field `planned_date_begin_formatted` and used it only on the project_enterprise module. The FSM app is using the `date_format` to display the date into the following format `HH:mm A` (08:00 PM for instance) Forward-Port-Of: odoo/enterprise#6826
Original PR description
PR linked to #40599 (community) As I removed the date_format, the FSM app crashed because it's using it. I added a field `planned_date_begin_formatted` and used it only on the project_enterprise module. The FSM app is using the `date_format` to display the date into the following format `HH:mm A` (08:00 PM for instance) Forward-Port-Of: odoo/enterprise#6826
Task ID: https://www.odoo.com/web?#id=2083554&action=327&model=project.task&view_type=form&menu_id=4720 PAD: https://pad.odoo.com/p/r.2f687b0da932d17f7091bb3be6ae1625 Forward-Port-Of: odoo/enterprise#6173
Original PR description
Task ID: https://www.odoo.com/web?#id=2083554&action=327&model=project.task&view_type=form&menu_id=4720 PAD: https://pad.odoo.com/p/r.2f687b0da932d17f7091bb3be6ae1625 Forward-Port-Of: odoo/enterprise#6173