Project title should appear for tasks assigned to others
This seems like a very simple request, but is apparently not something that Wrike is able to do.
When I assign a task from one of my projects to a colleague, they are not automatically able to see the name of the project to which the task belongs. In my own workspace, the project name automatically appears as a "tag" next to each task (in My To-do view) and under the task name in window view, but in my colleagues' workspace they can only see the task name and not the project title.
Ideally I think that tasks assigned to others should also include the Project title by default (or at least the option to toggle this on and off).
I've spoken to the Wrike helpdesk about this and apparently their workaround is to either include more detailed task names, which outline the project title within them (this is extremely annoying for projects which have up to 300 tasks, and also makes the task names too long. This also isn't useful when using blueprints, as we would need to manually change the tasknames for each different blueprint to match the different project title); or their other workaround is to share the whole project with the assignee, which is also not a useful workaround for us, when we have casual staff who really only need to see their own tasks and don't need to be bogged down with the whole project task list.
I'm quite frustrated that very simple things like this aren't automatic features within Wrike. I feel that for the price we pay for the system, we should have better solutions and not these clunky workarounds.
It's a little mind-boggling that this isn't a standard part of their UI. It makes the entire platform incredibly frustrating & difficult to use, and should've been a no-brainer somewhere around step 1 when planning how this product works. That workaround is a joke.
I don't understand how this isn't a thing in Wrike. The workarounds that have been offered are awful. I've got a long-term renewal quote for ~$85,000/year sitting in my inbox and it's this and a couple of other things that are making me hesitate on pulling the trigger on that renewal.
I hope a serious solution for this is on the fast track on Wrike's development plan.
Hey Jemma — it's a continuation of this issue that we're seeing, and it has a bottom-up negative effect to the way tasks are viewed overall. Without that project/space title to give context to or sort by, it becomes unhinged. It's particularly annoying because it's all RIGHT THERE in the core organization of Wrike (spaces, projects, folders) — they just need to give the user some control to actually use it as a viewing/sorting tool.
Your exact issue: https://help.wrike.com/hc/en-us/community/posts/360038523494-Shared-Tasks-lack-context?page=1#community_comment_360010342074
Project view/sort: https://help.wrike.com/hc/en-us/community/posts/115002313449-Sort-Tasks-by-Folder-and-Project
Project view/sort 2: https://help.wrike.com/hc/en-us/community/posts/360038214574-Task-Sort-Order-By-Folder-Project-or-even-Space
Completely wild that this isn't already part of the system. The workarounds are ridiculous too. Surely this isn't that hard to fix in the grand scheme of things?
Had similar issues within our company as well. Answer for us is to prefix each task with the project name which allows users to see the project name quickly and easily. Not ideal I agree with all comments above.
Also get annoyed with tasks in a gantt chart without the table showing. If the task is longer than the duration you are viewing then you cannot see what the task is unless you click on it.
We're having a similar issue where we're trying to develop some sort of internal "best practice" to name tasks like "program name or department - project acronym - year - task name" and it's a lot to put into a task name that might just be "submit final copy to printer"
Sarah Dungey yeah, that's precisely the problem. Putting the effort to manual data entry is absurd when the hierarchical/organizational data is already there, is completely absurd. It goes against the entire structure of how a PM system should work (and how Wrike is already organized!).
This really shouldn't be treated as a feature request by Wrike that requires 60+ upvotes, because it's so basic. This kind of thing balances on the line between new feature and something that needs to be fixed because it's broken.
Precisely, this isn't a feature request. This is a bug report.
I had my health check call with my Wrike customer success manager yesterday and I brought this to his attention.
Hey everyone, thank you for all of your feedback. It has all been passed on to our Product team. I don't have an update for you right now, but as soon as I have one I'll let you know!
Has there been any correction to the issue noted above? Or is the workaround the only answer as of now?
Hi Susan Ferrara, welcome to the Community!
Right now, sharing works so that the tags (project titles) are only seen when the project is shared with the user for security reasons. So you can either share the whole project when assigning a task to someone or create the tasks with instructions for the assignees. If you have repeatable projects with tasks, you can create blueprints to add the instructions once and then use those blueprints as many times as needed.
At the same time, this feedback has been passed on to the Product team and they are aware of this ask. For now, I don't have an update from them, but if I do in the future, I'll make sure to let you know.
Please let me know if I can help you with anything else!
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
Hello,
Has there been any correction to the issue noted above? Or is the workaround the only answer as of now?
Thank you,
Hi Pier-Luc Beaulieu, thank you for reaching out!
There are no changes for this functionality, but it would be great to learn more about your use case!
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
Hello, has there been any update to this? Here is a use case. When a request form is submitted by a member of our company, we have several blueprint projects set up. It would be nice if the project name would automatically populate in the task name if we had some sort of *|Merge|* Field or Tag. We are experiencing the same issue as others have listed above. Our team receive notifications for tasks where you can't see what project it is a part of.
Hi Max Lauro, welcome to the Community 👋
As you're working with request forms a lot, have you tried mapping some of the answers to the title of the project that gets created after a form submission? It could be helpful in your case.
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
We're having a similar issue where our assigned approvers are unable to view the name of the project they are asked to approve things in. Is there a way to have the title of the project auto-populate in the description of each task?
Hello Tima Aflitunov, thank you for chiming in. May I ask if the project is shared with the users as well? Or only the task - an not the project that contains them - are shared with the appovers?
Thank you!