You can do this similarily with Flowsana but it takes longer to update
Is there any indication that this feature request is on ASANA’s development roadmap?
Looks like this has more than 50 upvotes. Any status on it?
I can’t get the video to play. Am I missing something?
Hi @Brian_Gorsky , Asana doesn’t make their roadmap public so there is no way of knowing. If there is a new update, it will get posted here.
Hi there,
is there any possibility to automatically add the project name as a prefix to each task in a newly template-generated project?
For example: Project is called “Product1” I use my template and enter the project name. Generating the task from the template every task thereafter is called “Product1 - Task1 …”
Thanks for your answers in advance
Greetings Martin
@Simon_Logé Can you share this video with me? I cannot play it from the thread. If you can’t can you please send me the basic steps to set this up in Zapier?
Each of our projects is associated with a project number, and we currently add this project number to each project task name manually. Its a chore, but worth it.
If the ID field could be the catalyst for populating a task name prefix it would save time.
In Wrike, when you set up a project from a template, or duplicate a project, you can add a prefix to the tasks - would be great if Asana had this too (my team members are not all willing to add the flowsana integration)
Just to be clear, only one person on your team needs to sign up for Flowsana and create a rule. That rule then gets triggered when any team member does the relevant trigger in Asana; there’s no need for other team members to even know what Flowsana is!
Any updates on this? Without this feature the board view is useless for anybody working on multiple projects. The list view does let you view the project for each task, but for anybody with 20+ tasks you cannot drag tasks from one category to another without scrolling super far down so that makes the list view kind of useless to.
+1 for this - adding “project name” to the list of variables you can use when creating rules, task templates, etc would solve this problem. The issue we have is the same as many others here, it’s impossible to tell what project a task is for on timeline/calendar views, preventing Asana from being a useful tool to view day-to-day scheduling and capacity for a team.
This is a default feature for some of your competitors. A bit disappointed to find this missing in Asana and all the hassles above to get Asana to even look into this, to be honest.