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?
3 Likes
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
4 Likes
@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.
2 Likes
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)
1 Like
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.
2 Likes
+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.
1 Like
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.
2 Likes
If Asana would simply make tasks show with their affiliated project name, that would also work.
Since we use project templating, every project of a particular type has the same list of tasks. When I look at tasks due or just the task listā¦I have a bunch of tasks with the same exact name and no indication to which project they belong. This is both a trivial fix to implement and one that is critical to task management.
1 Like
Hey all - If you donāt have Flowasana, I found a tiny work around for this in Asana. It does require a manual update, but its not nearly as bad as making the changes to each task individually.
- Create a custom field and name āProject Nameā - make sure its a drop down option
- Add in all of the different project names to this field that you think you will have.
- Create a custom rule that states: When a task is added to this project, set the Task Title to: Then use the populated fields for āTask Nameā - custom field āProject Nameā .
- Create another custom rule that states: When custom field is changed āProject Nameā - Set Task Title to populated fields āTask nameā - āProject Nameā
Add these to your templates, and then the only manual thing you will need to do is update the custom field to the project name one time, and the rest should take care of itself.
Hope that works out, iāll be testing it myself with some new projects I am setting up.
This only works for tasks and not approvals.
Hi @Charla_Rowe,
That Flowsana rule will work for approval tasks as well. If itās not working properly for you, please contact our support so we can get it resolved for you! (Also note that screenshot is of our old rule builder; the current one is much better!)
The flow rule works, but I canāt add the project name into an Approval task. The only options are task info, people info, date info, and custom field info. So I canāt add the project name.
I basically have a template for a monthly deployment. I am auto-creating approval subtasks
but sometimes tasks have approvals in multiple deployments. So I wanted to add the project name to the approval subtask but there isnāt an option for it.
My bad. I didnāt read the thing closely enough. Iād have to create a custom field. Youāre right - that would work.
1 Like
Any updates on if this feature is available or being considered at least. Shocked that such a basic feature is missing in a product like Asana!
1 Like