Identify what Project a task belongs to

I agree there are opportunities for improvement here.

What we currently do as an organization is we prefix the task name with the project name so it looks like this "Project #1 - Task #1". It's something that can be added rather easily either through the "create from blueprint" menu. We use a request form for new projects so I have had to write an automation using Wrike Integrate that detects when a new project is created and adds the project name as a prefix to the tasks in our project blueprints.

Hope this helps.

Yes, as i mentioned, we do use the blueprint tool to pre-pend a project number (a project description is simply too long to add to each of the 150-200 tasks that belong to each project).

The problem with this is that its hard to remember what project number belongs to what customer & project. We end up needing a cross-reference table, especially when generating reports when sharing schedule snapshots, calendars, and reports to contractors and people outside of our org who are not as familiar with all of our project numbers.

Calendar example:

Workload Example:

As you can see here, we need to organize our project tasks with sub-folders since our projects a relatively large. This further complicates things, since the folders are reported as the parent, not the project. Reporting by project is challenging since the report wants to always group on FOLDER rather than project.

Don't get me wrong, Wrike is amazing and we love it.. but we are VERY project oriented, and this seems to be just a bit lacking. 

I agree, it's definitely a blind spot in terms of functionality. I've brought it up multiple times and I always get the answer to just add the project name as a prefix. It's not ideal and a more mature solution definitely needs to be developed.

This is an interesting discussion, thank you for sharing your thoughts here, Timothy Livingston, John Bibbs! 🙌 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

As I look through the Wrike community, I find many people having trouble identifying what project a task belongs to. 

Many posts identify one area of Wrike where this happens, and causes problems for the poster. Each of those posts has a collection upvotes.

When you start tallying all the upvotes across all of those posts (which are essentially identifying the same problem within different areas of Wrike) I believe we would find that we have enough upvotes for a fix to be considered by the development team.

Timothy Livingston All the feedback from the Community is passed on to the Product team for consideration regardless of the number of votes. The votes help the team understand the popularity of the requests, and they may add certain ideas to their development plans. Here's a post explaining what happens with Product feedback after you post it 👍 

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

Did this ever get implemented?

Hi Jeff Howard, welcome to the forums 👋

Could you please let me know if you use tagging? 

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