Automatic project name prefix added to each task

Hi all,

Does any one know how to automatically add the name of the project as the prefix for all tasks that belong to that project?

This is just a work-around that could allow us to quickly see what projects everyone is working on in the workload view, which currently only allows to display tasks, but not projects.

I know you can automatically add prefixes when you duplicate the project, but that's not what I'm looking for. I need to be able to add tasks and have the project name automatically inserted in front of the task. Our projects are non-standard, so even if I duplicate a project and thus get all the prefixes, if i then insert a new task, this new task doesn't have the prefix added automatically.

I'd be grateful for any suggestions.

Thank you!

Mat

Find more posts tagged with

Gathering votes

Status: Gathering votes

Comments

Permanently deleted user

Hi Matt,

Currently, the task name doesn't take any attributes from the Project or Folder name unless you duplicate like you mentioned.

It would be great to hear a little more about your use case or even why duplicating won't work for this? Looking forward to your reply 👍

Ezra Moore

Yes! Please add this. I agree completely with Matt.

Permanently deleted user

Moving this to Product Feedback so other can up-vote and discuss 👍

Kate Shaw

Hi,

When you duplicate a project, I see you can add a prefix for tasks…

Thus I set a template project up, to use just for duplication purposes when setting up new iterative projects…

However, after I duplicated the template and renamed it as the new project, the prefix didn't get added when I added new tasks to the project.

How do I make that happen pls?

Thanks

Jason Pontius

Why can you add task prefixes when duplicating but not to existing projects? Why isn't this an option to set for a project whether it be through a request form, duplication, or manual option setting?

Permanently deleted user

Hi everyone! This is currently not planned by our Product team, but they are continuing to discuss the possibilities. I'll let you know as soon as I have an update.

Laura Boylan

In the absence of an official, built-in solution, it's possible to achieve this via Wrike Integrate (paid add-on). I created an example recipe showing how this could be done at https://www.workato.com/recipes/1102718, and posted in the Best Practices section on how it works at /hc/en-us/community/posts/360039269654. (This example isn't robust enough for all needs, but for simple project setups with limited sub-folder nesting where tasks are always tagged to a single folder or project, it should work fine.)

Permanently deleted user

Hi @Laura Boylan, thank you for the Wrike Integrate recipe!

Tiffany Avory

Hi,

has there been any update on this recently. The option to add the project title as a prefix to all tasks within the project when manually creating a project would be very useful

Cansu Yetisgin

Hi @Tiffany Avory, thank you for bumping this thread! Not at the moment, we'll be sure to let you know if there are any updates🙋🏻‍♀️

Juan Muttoni

Hi Community! I'd like to mention there is a new action in Automation that allows you to automatically add prefixes to new or existing items. You can learn more about it here.

Would you please let us know if this enhancement fulfills this suggestion? Looking forward to your feedback!

Morgan Hay

What would be helpful for our team (and I think this is the intent of the original poster) is to have the prefix be dynamic and let us choose "Project Name" or "Parent task name" or some variable. Speaking for our team, it won't always be the same prefix in front of each task, so it would be helpful for it to be dynamic.

Elizaveta Bogdanova

Thank you for your additional feedback @Morgan Hay.

We're hoping that this new addition Juan mentioned above would be helpful, but we'll also continue passing the feedback from this thread to our team 👍

Welcome to the forums 👋

Isabell Dabergott

Hi! We are also missing the possibility of adding a dynamic prefix. Is there perhaps any update on this?

Elizaveta Bogdanova

Hi @Isabell Dabergott, welcome to the forums 👋

Can you please check out this article where we explain how this can be achieved with automation and let me know if you need any further guidance?

Isabell Dabergott

Hello and thank you!

Sorry, I was a bit unclear. I have used the automation function but would like the automation to have the possibility to add dynamic fields. As some people suggested above. As it is now, I have created multiple automations for adding prefix to a new task, just because I need the prefix to be different in different folders, but they all follow the same structure so having a dynamic field would make sure only one automation would be needed.

Juan Muttoni

Thank you for the additional details @Isabell Dabergott, I've shared your case with our dedicated team 👍

Jacob King

The usage of variables when renaming (or appending a prefix/suffix to) tasks would be immensely helpful. In our use case, we have a request form that's used to generate a project (from a blueprint). In the request form are a handful of custom fields. Depending on the values of those fields, one or more subtasks get opened dynamically using automation rules. Currently we don't have a way to append the ID number of the project to the front of those tasks using automation rules. You could do this if the subtasks were a part of the project blueprint, but we don't always need all of the tasks, and some task types are mutually exclusive. I included an example of what I'm looking for below:

Juan Muttoni

Hi @Jacob King, welcome to the Community! Thank you for sharing your use case with us, it is definitely an interesting one. I have passed your feedback on to our Product Team and please rest assured that we will keep you informed if there are any changes applied 👍

Also, I'd like to mention that you can check our New to Community forum to discover all the resources you can find in our Community 🙂

Simone Darphorn

The underlying reason for wanting to have the project code in the task description is most of the time for a better visualisation in the workload overview. Instead of adding the project code in the task name, my preference would be that in the workload planner you could configure the text label of the task. And you could select which properties of the task are displayed. E.g. <Project Name> - <TaskName >.

Also the colors of the task in the workload are based on the task status. It would be really nice if it could be configured to color by project or other task property.

with kind regards, Simone

Basudha Sakshyarika

That's a wonderful suggestion, Simone! Being able to configure the text labels of tasks on the workload chart and use color for status would be a great solution. Thanks for sharing. I have passed it on to the product team as well. 👍🏽

Simone Darphorn

Because this issue comes back in among different posts, but is most of the time focused on work around of using the project code as a prefix within the task name (requiring a annoying setup of automations to accomplish). I have created a new post as a feature request under product feedback. I will be very interested if and when it will be incorporated into the product.

Project Name visibility for Tasks overviews (Workload Chart / Dashboards) – Wrike Help Center

Looking forward to any updates on this ;-)

Basudha Sakshyarika

Hi @Simone Darphorn! Thank you for creating a separate post and suggesting possible solutions. Really appreciate it. I will pass it along to our development team for consideration. 👍🏽