Custom fields on other member's task lists should be visible

English Forum Product Feedback
21

I don’t work for Asana and I’m not necessarily defending this feature, but it is a feature, not a bug (a bug is when software doesn’t work as designed, and in this case, it is working as Asana designed it).

It’s not a technical matter - as you say, technically it can be allowed - but rather Asana built it this way for privacy. As explained to me, they consider one’s My Tasks as an area where a user should be able to “do things privately” without worry about other users seeing it. Again, not necessarily defending it, just explaining.

One thing I will note: since they implemented this design, they have recently introduced more access control capabilities on custom fields in general, so maybe that was a first step to changing this My Tasks behavior. Just speculating…

1 Like
22

You can’t explain to me why something should be private in a business software where the user explicitly shared access.
If I have access to every single component (tasks, projects, fields, etc.), even created the custom field for the user as an admin, it should be visible (or at least an option to be) to me as well.

Where else does Asana hide information from other users where it shouldn’t?

This software is not working as designed (or at least not as advertised in my opinion) and that’s why I still call it a bug.

Don’t get my wrong, I’m very happy with Asana. I pay a lot for the whole company/team and we couldn’t work without it. But this is a little bug which makes our basic process of collaboration harder than it should be.