Feature request: Configurable hierarchy behavior for multi-home items (prevent double listing and preserve context)
Context
-
We run programs with two layers: execution projects (where work lives) and phase projects (for visibility across M1–M6).
-
Component project tasks live in execution projects, but also in relevant phase projects (multi-homed).
Problem
-
When both a parent task and one or more of its subtasks are multi-homed into the same phase project, views and reports list each item separately. This looks like duplicates and inflates counts.
-
When a subtask is multi-homed to a different project than its parent (typical in phase tagging), the subtask appears without its parent context, making it hard to understand where it sits in the work package.
Example
-
Execution project “Device HW” has a parent task P (phase M3) with subtasks S1 (phase M2), S2 (phase M3), S3 (phase M3).
-
Phase project “M3 HW Freeze” currently shows P (if multi-homed) with S2 and S3, and again S2, S3 as separate rows (problem 1). We need either a consolidated view or only the leaves.
-
If only S2 and S3 are multi-homed to M3 (parent P is not), the M3 view lacks the parent branch for context. (problem 2)
Requested capability
-
Add configurable hierarchy rules for items so teams can choose how parent/subtask relationships render across different homes without double counting and without losing context.
- Add a configurable mode that disables listing subitems as standalone items and always renders them under their parent for context, even when the parent is not a member of the project.
Why this matters
-
Prevents false inflation of work and improves signal-to-noise in phase reviews.
-
Preserves context when a subtask spans projects/phases without forcing rigid one-level tagging.
-
Reduces admin overhead maintaining separate “summary vs leaf” saved views and ad-hoc filters.
Hi Teemu Nurminen, thank you for clearly sharing your feedback here. It has now been forwarded to our Product Team. In the meantime, let's see how many upvotes it receives from our Community members. If there are any updates, we will be sure to share them 👍
Rohan V Community Team at Wrike Wrike Product Manager Werden Sie ein Wrike-Experte mit Wrike Discover
Rohan V Wrike Team member Werden Sie ein Wrike-Experte mit Wrike Discover
Hi,
The classic Gantt handles multihomed tasks well. Subtasks show once under their parent, even when both are tagged to the same project.
In the new Gantt and Task Table, both parent and subitems appear separately, which clutters the view.
It’d be great if the new views followed the classic behavior, showing subtasks only under their parent.
Also, adding a subtle “shadow” parent for subtasks that live only in the root would help keep context clear.
Unfortunately, I cannot share a clear screenshot of the issue, but you can imagine that in a program with about 10 projects and hundreds of interdependent tasks, the view becomes extremely crowded. Full of duplicate items and excessive dependency lines. Below is a demonstration of the same Phase project in new Gantt (left) and classic (right) charts.
Thank you, Teemu Nurminen, for getting back to us and providing additional information, this is helpful. I’ve also forwarded your comment to the responsible person 👍
Rohan V Community Team at Wrike Wrike Product Manager Werden Sie ein Wrike-Experte mit Wrike Discover
Rohan V Wrike Team member Werden Sie ein Wrike-Experte mit Wrike Discover