nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Ability to detach subtasks from Table view

Daisy Hibbard

Hello Wrike team! A huge quality of life improvement would be the option to right-click and detach subtasks from the Table view.

Currently we have to:

Click into the parent task
Click "subitems" on the little nav bar OR scroll down to them
Scroll through the list to find the one to detach
If the list is too long there's an additional click to expand them all

This extra time adds up fast, especially for anyone managing projects. We have some tasks with large descriptions and it can take several seconds for the parent task to load the subtasks.

If this option is added to the right-click menu, I would expect to see it above or below "Outdent".

Thanks for the consideration!

Find more posts tagged with

table-view

subtasks

Gathering votes

Status: Gathering votes

Comments

Chris DeFelice

Can't this already be done by adding the Location column to your table view?

Elizaveta Bogdanova

Hi @Daisy Hibbard 🙂 Thanks for the feedback!
Can you please share a bit one what happens next to the detached subtask in this scenario? Do you not need it anymore or do you need to move it to a different location (and if that's the case, what do you think of @Chris DeFelice's suggestion on the Location column) ? I'd appreciate the context 😌

David Simmington

When you mention detach, how does this differ from outdent?

Daisy Hibbard

@Chris DeFelice The Location column trick only works for folders and projects. So, unfortunately not applicable for removing a subtask. :( But thanks for jumping in! Even if the parent task showed up as a Location source for subtasks, I'd still have to click into the field, find the location to remove, and then click to remove it. A little more work than right-clicking and detaching.

@David Simmington Outdent just un-nests the task from its current location and bumps it out a notch. It's wonderful if you accidently drag and drop a task into another, creating a subtask structure. Detaching completely removes it from the current Location (meaning you shouldn't see it on the Table view anymore).

@Elizaveta Bogdanova The biggest use case I have for this is with large, cross-functional projects. We have a process where we roll into a 30-day "closing" phase and complete as much post-launch work as possible. After that, any remaining active tasks gets kicked out of the project and live elsewhere—sometimes completely isolated in one space, often times still cross-tagged to two or more spaces for visibility.

As we get closer to that 30 day mark, I check in with stakeholders on the remaining tasks, and we often make the decision to just go ahead and move the tasks out of the project. So I'm usually only removing one or two tasks at a time, but sometimes several times a week. Annnnd a lot of times, as we're reviewing the tasks, I have to open it to make notes in the description, edit locations, etc. When a subtask is open, there's no option to detach it from the 3-dot menu (that would also be RAD!!). So I have to click the breadcrumb trail to find the location I need to remove it from (again, sometimes it's connected to multiple parent tasks), wait for the correct task to load, scroll down to the subtasks, then scroll to find the subtask to detach. We probably have 15 people here who remove subtasks like this.

If the tasks are attached directly to the project or nested in a folder, then I can use the Table view's bulk edit "Remove from" feature to remove them, but it's still a slower process with additional clicks.
[my main focus/use case] If the task is nested inside another task, I can't use the "Remove from" bulk edit option, I have to click into the task, find the subtask, and then right-click to detach it. These tasks always have one or more tags applied so when I detach it, it always has a place to live.
- Complexity note: We heavily utilize a custom task type called "Bucket" because there is still no way to view projects or folders on a Board view. Several years ago I created this workaround, specifically for our Agile Marketing team to keep like-work nested together, but the paint bucket icon is a quick, visual reminder for team members that it's a bucket full of [parent] tasks. For large, cross-functional projects, we divide the work into "Buckets", and those buckets often get tagged to Board views, mostly for various agile teams to keep like-items together, but it also gives us the ability to add start and end dates so we can project manage more efficiently. I realize this might have created an "us" problem, but we've found such success with this customization! Let me know if I can provide more details. :)

Chris DeFelice

Location works for tasks and subtasks. I assume you mean it doesn't help because it only shows the direct parents and not the top level task or project.