Commenting to @assignees for a project

I would LOVE it if the @assignees would work for everyone assigned tasks and subtasks within a project to work. For example, right now the @assignees works only at the Task or Subtask level. I want to talk to everyone on the project using this @assignees handle.

Ideas? Upvote?

Thanks,

Andrea

Find more posts tagged with

On hold

Status: On hold

Comments

Tim Schoffelman

Hey Andrea - so just to make sure I'm understanding, can you take a look at the example below and see if I'm getting your idea.

ACME Project Folder

ACME Project Management Folder (Assignees: Bill & Bob)
*** ACME PM Task 1 (Assignee: Bill)
*** ACME PM Task 2 (Assignee: Bob)
ACME Production Team Folder (Assignees: Billy Bob & Bobby Bill)
*** ACME Prod Task 1 (Assignee: Billy Bob)
*** ACME Prod Task 2 (Assignee: Bobby Bill)
ACME Invoice Task (Assignee: Fred)

If you're on the ACME project folder and comment there @assignee, Bill, Bob, Billy Bob, Bobby Bill & Fred will all get notifications? If you were on the ACME Production Team Folder and comment @assignee, then only Billy Bob and Bobby Bill will get a notification?

Thank you!

Andrea Bonk

@Tim - I want use the @assignee to talk to Bill & Bob assigned to the ACME Project Folder. We use team folders but in our world if I @mention everyone in that Team Folder too many people would get a message.

Thank you!

Andrea

Tim Schoffelman

@Andrea - that's a great idea. We have team based groups, but people often complain of not using them b/c too many people will get the notification. Nice suggestion.

Meghan Sharer

This would be really helpful. When our project leads have general updates, they tend to communicate that via email. If they could send one message to everyone assigned a task within their project, we could keep those communications within the project in Wrike. 👍

Marcy Kelley

It's not a great user experience that the @assignees mention doesn't work at the project level, and only the task level. Please consider adding this to projects as well as we're at 58 upvotes.

Juan Muttoni

Hi @Marcy Kelley, thank you for sharing your feedback with us! As a workaround, you can mention @followers, as all assignees are automatically added as followers - although, I understand this is not exactly what you're looking for.

We will keep you updated if there are any changes 👍

Kelsey Rudolph

Hi @[Deleted User] - I noticed that @followers doesn't work for me as assignees don't get added as followers on our projects:
Is this a set-up error within the blueprint on my end? We have hundreds of blueprints - it'd be a lot of work to match followers to assignees especially as assignees change.

Elizaveta Bogdanova

Hey @Kelsey Rudolph, I've asked our Support team to look into this for you 👍

Elisa Brown

When you use @assignees in a comment on a task, who receives the notification? Is it all assignees in the task and it's linked sub tasks? Or just the assignees on that single task?

Rohan V

Hi @Elisa Brown 👋

Welcome to the community! 🙂

When you use @assignee for a task, only the specific assignees for that exact task are notified. For example:

If you @assignee the main task (e.g., Test 1.0), only David Martin, who is the assignee for the main task, gets notified. Julia Hernandez and Amy White, who are assigned to the subtasks, do not receive the notification.

Hope this helps! 👍

Karen van Veldhoven

Do we have an update for @followers? My team is under the same impression that @followers should notify all the assignees for that project but I have not seen that actually work.

Rohan V

Hi @Karen van Veldhoven 👋 Normally, using @followers should notify all assignees as well. I'll go ahead and create a Support Ticket for you, and one of our experts will be in touch shortly to assist you further.

Basudha Sakshyarika

Thank you, everyone, for your comments and feedback. 🤝 Since this suggestion has received more than 60 upvotes, I have added the appropriate status to it. I have marked it with Backburner ⌛️. It means the product team is interested in this suggestion; however, it is not yet part of the product roadmap. We will let you know when there's an update. Thank you! 😊

Anna Giacobbe

Definite upvote from me here.

Seems a little odd to me that this isn't implemented yet. We communicate at times at the project level and we can't @mention "assignees", nor "owners" (I tried!) - it can be cumbersome to have to @mention every individual separately when this feature already exists for tasks.

Anna Giacobbe

Just a follow-up on this. Support has mentioned the following:

The reason you cannot use `@assignees`on projects but can use it on tasks is due to how Wrike is designed. • `@assignees`is specifically designed to work only at the task level. This is because tasks have assignees, whereas projects do not have assignees in the same way; instead, projects have owners. The `@assignees`mention is used to notify all assignees of a task, but since projects do not have assignees, this functionality is not applicable to projects.

Saying that projects don't have assignees is rather misleading, in my opinion, as the native Assignee field appears on projects (and there is no Owners field). I think a simple fix to this would be to allow us to simply @assignees on projects to comply with the naming of the native field that is usable for this work type, despite the logic/idea is that there are owners on projects and not assignees.

Basudha Sakshyarika

Thank you @Anna Giacobbe for your feedback and for highlighting how @mentions at the project level can be improved. I’ve shared your comments with our product team and will keep you in the loop with any updates. 👍🏽