Remove Ghost-Tags from Subtasks
We would like to have the option to remove the ghost tags from subtasks, and here is why, explained with an example:
Our Folders are:
- interdisciplinary
- graphic
- pr
- ...
For example if we have to write a blog entry, this is a task in the folder "pr". If this blog entry needs some images, this is a subtask for the blog entry. But this subtask has clearly to be in the folder "graphic". So we add "graphic" as a tag to the subtask. But because we can't remove the tag "pr" from the subtask, the tracked time for the subtask would appear in both reports: the report for pr and the report for graphic. So the total of all tracked times would be higher, then the real effort, which we had.
I would be really happy to find a solution for this problem.
Hey Martin, it's a good request and question! I can see some people have agreed by voting 🙌
Ghost tags are purely informational, simply letting you know the parent location for where it resides.
Wrike is flexible so let me explain my own thinking when I'm creating something similar in my account.
I would not usually create this 'graphic' job as a subtask to the blog, it's more like a dependent task - you can't publish until it's done so it should stand alone.
So, to me, it sounds like the Blog article itself is a project made up of tasks, one of which is creating graphics. It's an important item, it deserves its own task instead of 'sharing' a task with you by completing its subtask 🙂
For me, my Project would be like the example below.
Project: 'Create Blog Article'
Tasks:
Now, when you move the 'Graphics Design' task to the Graphics Folder, and you have greater flexibility of where this task 'lives' for reporting purposes. You can remove it from the PR Folder if needed, and keep it in the 'Create Blog Article' Project or vice-versa - wherever you need it to be. Right now, you're not dealing with any ghost tags anymore so reporting and folder tree structure are a lot easier to set up.
But this begs the question, when do I use ever Subtasks? You could use them here, of course, but considering you need a cross-function collaboration, it is going to affect your reporting. Why? Well you're saying to the graphics team, 'I need your help to complete this blog task', so when reporting it will show that they helped complete this task because they did.
Instead, ask them to help complete this project. Moving everything up a level allows you to separate what task you need them to do, without making them responsible for the tasks you're responsible for and then this won't show up on everyone's Reports.
Hope that makes sense, happy to keep chatting about it so let me know your thoughts - and sorry for the delayed response on this one. 🙏
Running into this for when a subtask is in a different Sprint (and therefore a different Sprint Project) than the parent task.
Thank you for reaching out about this Regina Ball! Did you have a chance to read Stephen's advice on this above? Could moving things up one level help in your case? I'd be happy to discuss 😊
Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with Wrike Discover
Lisa I did, but that approach won't work for us - we don't use Projects as typical projects because it doesn't work with our Agile framework. Instead, for what some might consider large enough for a Project, we use a task with subtask, or a variety of tasks with dependencies. I'm trying to make it easier for the team to visualize dependencies (we avoid using the Gantt chart view), which is why I was leaning towards subtasks, but the inherited tags/labels are causing confusion.
Regina Ball Got you, thanks a lot for sharing those details! I'm passing your feedback to the Product team 👍
Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with Wrike Discover
Lisa Thank you!