Email notifications and project names

Hi Alexa, thanks for your feedback. You should be able to see the Parent Folder in the email body information, however, the task name is shown in the subject - is this where you'd like to see the parent Folder's name? Thanks

I use several sub-folders with my team and therefore the project name is not available anywhere in the email. It would be great to be able to adjust the email settings to the correct information for notifications, or if all the sub folder names were included somewhere in the email body. 

See screenshot attached. The name I need is presumably in the ellipsis seen in the email subject.

Also, I would be great if all the changes of many tasks of a project appears on ONE email, like a summary of changes in the project. 

Andrea Rosales "Gracias por existir Ctrl+Z"

We are in the same boat as we are creating Projects that have our internal Proposal # and short description as the name of the Project. We then have our projects divided into five subfolders with specific tasks within each of those subfolders. When a notification is sent, it only shows the subfolder name and you have no idea what project it is for.

This is how the notifications are sent

Our projects will start from a Request Form most of the time, so the only work around I have at this point is to map a question to add a Prefix to all folders, tasks and subtasks, which we used Customer Name. While this is better than nothing, it still doesn't provide the Project Name (our proposal #), which will be an issue for some of our larger clients that have multiple projects happening at once. It also can be quite long depending on their company name versus a six digit proposal #. 

The lack of project name in all types of email notifications is frustrating. I agree with the above comments, as well when we get notifications of new tasks, the parent nor the project is listed in the email at all. Here is an example of a task notification; it does not show any reference to the parent folder or the project. Why is this information missing from the emails?

Is there a fix to this? Communication is a critical aspect of Project Management. The ways emails come as of now, result in confusion leading to less productivity. Based on this, i cannot even use email client rules to filter these emails to appropriate folders.

Hey everyone, thank you for all of your use cases, they help our Product team in their conversations about future developments. I have no update as of right now, I'll keep you posted 😊

Hi Wrike,

I am onboarding customers, and these mail notifications as-is are not necessarily considered to be one of the strong points of the Product. However please note that these notifications are VERY VISABLE, like..... every day.

Hence I don't understand that no time was spent on this improvement request for the last 3 years, but time is freed up in development to create very sophisticated new features, but which are only used by a small portion of the customers. Everybody however is using notifications. This would be a big impact improvement, no?

I agree that the lack of improvements on this is disappointing. Can we please get some attention on this?  Notifications should include the Project and the parent folder. Just the parent is never enough information, as WRIKE ADMIN has shown above. If the parent folder was shown as the immediate location as well as the top project, it would be clear what project it is in.

Hi Arthur Dewaal, Jason Pontius, thank you for bumping this thread! Your feedback is passed on to the team, and once we have an update from them, we'll make sure to let you know here!

Please upvote the original post at the top of this page if you haven't yet 👍

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

Is there still no update on this?  This is such a basic request and completely frustrating that there is still no resolution.

Simon Hwang I support and agree your follow up. This is not difficult, and it affects everyone. Can everyone please upvote this so we can get some attention and get this improved? I'm tired of searching for items that match the notification because the project isn't included.

@... I don't understand why you need more feedback and use-cases for this issue. We have clearly described the issue here. WRIKE ADMIN  did a great job of detailing the scenario.

Bottom line is that the notifications don't include the project name and it is very difficult to know where it comes from. That's it. That's the issue. No more use-cases are necessary. 

In my opinion, this is less of a feature request, and is closer to a bug. It's missing information that is needed on notifications; not a request for something new.

This is another example of something that has been reported for 3 years and has never been addressed. Come on Wrike!

Everybody (Alexa Hibbert, Andrea Rosales, WRIKE ADMIN, Srinivas Karanam, Arthur Dewaal, Simon Hwang) please make sure that this is upvoted and add comments to get this issue prioritized.

Thank you everyone.  

Adding a comment here to refresh this thread. I doesn't seem like this has been addressed since this concern was first raised in 2018 (nearing 6 years). This seems to be basic functionality that many competing products have implemented since day one.

Thank you, Eric Joyce, for pinging this thread.

As you can tell from my comment 2 1/2 years ago, I don't understand why this is such a big deal to address. It is a miss by Wrike, and it needs to be resolved. I get so tired of not knowing what project notifications are from. Even those that include the "parent" are usually just a folder or parent task of a subtask, but not the actual project. So these are often useless.

And to look back over this thread and see a repeated message of "not now, but we'll keep you posted" falls short of Wrike making this minor tweak to make notifications actually useful.

I'm going to re-up this thread as well. This is also a big issue with other Wrike functions as well like kanban/board view. I'm trying to transition my team to a kanban structure and I'm left with a board that shows a bunch of tasks with no easy way of seeing the project, which defeats the point of kanban. This is due to the same issue that causes the notification problem. I understand that project management systems are based on a folder/project/task architecture but all they'd have to do is duplicate the project name to a reference field in the data warehouse whenever the project is created/updated then reference that data in emails, board view, etc. It'd also fix the issue for the vast majority of users if they just added the next 1 or 2 levels up in the structure to the right in any of these examples - plenty of room - so it'd odd that this hasn't been addressed in years. 

Thank you everyone for your continued support! Plesae, rest assured that we are passing all your comments on to our Product Team and we will keep you informed if any changes are implemented. 

Thank you for sharing your use case in this thread Travis Balthes, examples like this one help our Team better understand the positive impact this option would have 👍

We’re also eager to have the project name included in the notification emails, as we use sub-phases and folders within projects. Assignees often struggle to identify which project a task belongs to, especially since many of our projects rely on blueprints, resulting in identical folder names across projects.

Rohan V Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Rohan V Wrike Team member Become a Wrike expert with Wrike Discover

It's hard to believe that this is still an open feature request after so long.  We also would like to have the project name included in to-do and digest emails.  Thanks

In general, throughout Wrike this is a problem. So many things only show the "parent" object, and not the overall project it lives in. This is annoying and frustrating. Email alerts, dashboards, reports, and so on, only shows the Parent folder or immediate project. As stated throughout this thread, once you create a structure of folders and such, you lose the reference to the actual project. 

We do use prefixes, but man does that just make things long and clunky. Having to prefix every item with a project reference is ridiculous. It's laborious and makes all of the naming extra long. We just need to see a reference to the project, not only the parent container.

Wrike needs to show the root project, not just the parent container. It does me no good to see the parent folder name as "Phase I". Phase I of what? That could be any and every project.  We need to see a reference to the Project itself. 6 years now and we still don't have this.

Jason Pontius the problem is that we're all still here 6 years later haha! It's clearly not annoying enough to drive customers like us away from the product and it's not a billable feature so no reason to prioritize it.

Travis Balthes I don't think that all users think about some of these things and trying to get people to hop on board and upvote or add their opinions is difficult. There are a number of items that have been out here for years with no resolution and getting enough interest to push it forward is hard, even though it's a critical feature of most PM tools on the market.

Thank you for the feedback, everyone 🙋🏻‍♀️ This feature is not currently on our short-term roadmap.

While it would be extremely helpful, the complexities of cross-tagging and ability to create deep structures make it challenging to identify the parent to mention in an email. One approach could be to consider adopting a naming convention, as suggested by Rohan above. Please feel free to share your thoughts on this. 👍🏽

Basudha Sakshyarika Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Basudha Sakshyarika Wrike Team member Become a Wrike expert with Wrike Discover

I am also missing this functionality. When @-mantioning people in the organization that are not daily Wrike users there is always confusion regarding what project the resulting e-mail originates from.

Interesting to see that when the Wrike-bot sends out reminders/information about the status of tasks and sub-tasks the project name IS included!  It is CLEARLY then not a matter of new functionality, it's a programming bug that should be fixed ASAP!

This example of a Wrike-bot message in Outlook is triggered by the cancellation of a sub-task. BOTH the head task AND the project name are included!