Hello everyone,

I’m working on Odoo 18 (SaaS) and I’m trying to understand the limitations of Project Sharing when it comes to custom fields on tasks.

Context

• Model: project.task

• Environment: Odoo 18 SaaS

• Feature: Project Sharing (shared project with portal users, “Edit” access)

• Custom field created via Studio:

  
  

  • Name: x_studio_ding_dong

  • Type: Char

  • Stored

  • No groups restriction

  
  

I located the view used by Project Sharing:

project_sharing_project_task_view_form

When I add the custom field to this view, for example:

<field name="x_studio_ding_dong"/>

the task page in the shared project no longer opens.

The backend works fine; the issue happens only in Project Sharing.

Console error

In the browser console I get the following OWL error:

[Error] OwlError: An error occured in the owl lifecycle
Caused by: Error: "project.task"."x_studio_ding_dong" field is undefined.

From what I can see, OWL fails because the custom field is not present in the JS model used by Project Sharing, even though the field exists server-side.

I also confirmed that:

• readonly="1" does not change the behavior

• ACLs and groups do not change the behavior

• QWeb directives (t-if, t-esc) are forbidden in this view (as expected)

Question

Is it by design that Project Sharing in Odoo 18 does not support custom fields (x_*) on project.task, even for read-only display?

If so:

• Is this limitation documented anywhere?

• Is there a supported way to expose additional task data to shared projects, or is the recommendation to use the classic Portal instead?

Thanks in advance for any clarification.