Post by angloz »

After installing the module, we have lost the field activity_user_id ( Responsible User), which was used to assign the task to a responsible employee.

We can see there is a visible field called employee_ids (linked employees) but it's read only. How could we assign the task to a user ?

We also see there is a button "assign to me", when the task is not assigned to the logged user. Pressing it will add the user to the field linked employees. But we still need to edit this manually for best management.

We have manually comment the xpath in the template
bryntum_gantt.project_task_view_form
<!--<xpath expr="//field[@name='user_ids']" position="attributes">
<attribute name="invisible">1</attribute>
</xpath>-->

Now we can manually assign it to an user, and it will automatically add this user to the field linked employees. However, this is not something very normal. I think either leave only user_ids or set employee_ids as not read only.

Please check it.


Post by giot »

Hi, quick checkup to be sure - which version of Odoo have you bought the module for, and is it Community or Enterprise? Lastly, what's the module version you're running?

Our regular customer service rep isn't active this afternoon, so bear with me during intake here. Some of the following confuses me, so forgive the technical point-of-view where it's unhelpful:

After installing the module, we have lost the field activity_user_id ( Responsible User), which was used to assign the task to a responsible employee.

How did you lose it? Are Activities not working?

Task assignation happens through "user_id" (up to Odoo 14.0) or "user_ids" (15.0 and later) - aka "Assignee(s)" - by core Odoo.

"activity_user_id" comes from the mail.activity.mixin class, which is applied to many more models than Tasks alone. It's a generic field linking responsible users for Activities on Tasks rather than assignation itself.

We can see there is a visible field called employee_ids (linked employees) but it's read only. How could we assign the task to a user ?

By default, this happens through Assignees in Odoo. We are already reviewing the configuration that shows employees for clarity and usability reasons.

We also see there is a button "assign to me", when the task is not assigned to the logged user. Pressing it will add the user to the field linked employees. But we still need to edit this manually for best management.

"action_assign_to_me"—aka the button you're seeing—is a core Odoo functionality that we would rather not touch. It's present on any Task where "Assignees" is empty by default in the software.

Now we can manually assign it to an user, and it will automatically add this user to the field linked employees. However, this is not something very normal. I think either leave only user_ids or set employee_ids as not read only.

If the user has an associated employee, then yes it will populate the employees field. This part we are indeed looking into.

Could you be facing a straightforward technical issue with Activities on Tasks? I want to make sure I understand your situation correctly.


Post by angloz »

Hello,

Odoo 16 Community.

I think it's not related to the activities, those are working normally. It's only happening in tasks.

This view : bryntum_gantt.project_task_view_form is setting user_ids invisible, and the field employee_ids is read only (by database definition). There is no way to set or change the task user responsible.

Regards


Post by nivl »

Hi angloz,

We're going to be looking into this for you. There's a couple tasks dealing with user_ids and/or employee_ids that this fits into. I can't provide an ETA, but know that it's on our board.

Niels


Post by caalb »

The Kanban implementation of bryntum gantt replaces the assigned user on the Kanban tile with the assigned_employee, which is used by Bryntum Gantt.


Post by nivl »

Hi Angloz,

It's been a bit, but we're now on Version 16.0.2.1.23, with the previous version including a fix for user_ids and employee_ids you described. If you haven't updated yet, please do so and it should go better for you.

Niels


Post Reply