My to-do list - task location visibility

Hi all,

I'm also trying to find a solution to the problem above. In the "My to-do" section, when enabling the location field column, we are able to see only the immediate location of the task. When hovering over the location the full location path is visible. Is there any way to have this full location path, or at least a few more layers in location?

Find more posts tagged with

Comments

David Simmington

Hi @Romilly Benson, this is a current limitation of My To-Do. The Location column only displays the task’s immediate parent folder or project. Wrike does store the full hierarchy (Space > Folder/Project > Subfolder > Task), but in My To-Do the UI only exposes that full path when you hover over the Location field or open the task. At the moment there isn’t a way to configure that column to display additional hierarchy levels that I'm aware of.

Workarounds that could help:

1. Use a custom field for top-level context
Add a custom field such as Client, Program, or Master Project at the project level. Because custom fields propagate to tasks, you can display that column in My To-Do, which makes it easier to understand the task context without relying on the folder hierarchy.

2. Use Table View when hierarchy is important
If your workflow depends heavily on seeing the full structure, working directly in Table View within the project/folder hierarchy provides much better visibility than My To-Do.

3. Reduce folders where possible
If tasks regularly sit several layers deep, flattening the structure slightly (e.g., fewer subfolders) can also make the Location column more useful.

It would definitely be valuable if Wrike allowed either displaying the full location path, or choosing which hierarchy level appears in the Location column.

Pietro Poli

Hi @David Simmington ,
you mention "Because custom fields propagate to tasks".
My question is How they propagate?

David Simmington

When you add a custom field at the folder or project level, that field is automatically available on all tasks within that location. So any task inside that folder/project “inherits” the field, and you can fill it in at the task level or set a default value at the project level. That’s what I mean by propagation.