Visual Task Boards - Due Date field

Nathan Dupuis
Tera Contributor

Hello,

 

Free form visual task boards do not require a license, however the default task it creates is a project task.  This is ok, however the Due date field in the form is locked.  It unlocks if the user has a project_user role, which requires a license.  Is this regular behaviour, where a license is required to enter the due date field? Or maybe there's a config that would need to be adjusted. 

 

Thank you, 

1 ACCEPTED SOLUTION

Prinssi
Mega Sage

Hi Nathan,

 

There is one slight correction, the resulting PTASK from the Visual Task Board is a Private Task, and it is not directly related to the project management module, PPM.

 

The due_date field inherits access restrictions from the task table (see image below).


To be able to edit the due_date field, you could do one of two things:

  1. Add an applicable role to the user(s) you want to be able to edit the due_date field
    • Per the ACL below, that role could be catalog, task_editor, itil, or any other role that contains one of these roles
  2. Create your own ACL to extend the access to others beyond these roles (exercise caution with this approach, as it is possible to extend the access too far)

pschultz_0-1685566621465.png

View solution in original post

2 REPLIES 2

Prinssi
Mega Sage

Hi Nathan,

 

There is one slight correction, the resulting PTASK from the Visual Task Board is a Private Task, and it is not directly related to the project management module, PPM.

 

The due_date field inherits access restrictions from the task table (see image below).


To be able to edit the due_date field, you could do one of two things:

  1. Add an applicable role to the user(s) you want to be able to edit the due_date field
    • Per the ACL below, that role could be catalog, task_editor, itil, or any other role that contains one of these roles
  2. Create your own ACL to extend the access to others beyond these roles (exercise caution with this approach, as it is possible to extend the access too far)

pschultz_0-1685566621465.png

AJ2025
Tera Contributor

Prinssi is absolutely right. You need to add the due_date on the form of the personal task to realise that it's coming from the base Task table. Now the only option is either give the user one of these 3 roles or create a separate role that doesn't have anything else but this write ACL.