We have projects where we want the task assignee to have visibility of the task they are assigned to without having full access to the project. The task uses custom fields that have been added to the organization library and access provided to everyone in the organization. We want to ensure that these fields are visible to the task assignee.
However, these tasks are not showing up on the assignee’s end. This visibility issue seems to be more recent. Is there any other field settings are task setting that needs to be changed so it is visible to the assignees or another workaround?
@Richard_Sather the fields have been populated before the task is assigned. However they are not able to view it. With our current workflow, we simply want the assignees to view the field data and not interact with it. Here is a screenshot of what it looks like on their end. There are about 5 global fields with data in them within this task.
Bottom line if assignees are set to viewer or commenter they can complete tasks, view the fields and not edit any fields (except assignee and due date).
Hi @Madhumita_Prahallad1 , it looks like you have the new task details pane update and that might be the cause, different to the expected behaviour I mentioned above.
If the user doesn’t see it in a project, it may make sense that all fields are now no longer visible, even ones in the library, because they are now ‘grouped’ within projects in the new task details pane design.
@Richard_Sather, I just confirmed the behavior you described in the older version of the custom fields display.
I can’t easily set up a test of the behavior in the newer custom fields display.
Your speculation may be correct, but I’m not sure.
What’s always been odd to me in the old CF display behavior (which I just confirmed is still present a moment ago), and which you didn’t mention, is that you can actually clear the value of the custom field with the “x” at the end of the field, even though you can’t otherwise edit it. Also, the whole field row in the fields table appears greyed out (even though the “x” is there).
@Forum-team , I think this should be escalated either as a ‘bug’ of the new task details pane (which now combines projects with fields) or a ‘regression’ of previously expected behaviour, which will result in breaking existing workflows
Hi Everyone!
I am in contact with our engineers to give them the above feedback and check if this is an intended behaviour or a bug. Thanks for flagging!
Hi All!
I was able to confirm that the global custom fields should be visible in this case in a separate “disconnected fields” section, so that instance has been flagged as a bug. I’ll be in touch to inform you about any new developments!
@Madhumita_Prahallad1 Can you check if the custom fields are now accessible? They should be visible under a separate section named “disconnected fields”.
