⚡ Pre-multi-home tasks in project templates

If you want one of the following, this topic is for you:

  • Automatically add project template tasks to specific projects (for instance: to automatically add to specific departmental processes or even kick-off sub-projects with departmental templates)
  • Automatically run rules upon project creation.

Automatically add project template tasks to specific projects

You can pre-multi-home tasks in a project template, by adding them to another project:

When the project is created, the tasks will be added to this project/these projects

You can multi-select tasks as with normal projects:

  • Select first task, press shift and clicking last task to be included in selection
  • Hold down ctrl and click to (de)select additional individual tasks.
  • Mix and match to select the exact group tasks you want.

To select tasks without opening the side panel, aim for the blank space just in front of the checkbox:

When multiple tasks are selected, you can edit the added project(s) through the multi-select bar:

This might even be the start for kicking off a departmental project if you chose to convert this task into a project. In this way, the “parent” project will keep a neat connection to the “child” project, as it will keep the original task with a link to the project it converted into.

:information_source: If you’re serious about converting tasks to projects, make sure you understand Asana’s help article: Converting tasks to projects

Automatically run rules upon project creation

Although you might expect Task is added to this project triggers to work by using a template, that’s not what happens. I think this is either because the rules are only added or activated after the new project is populated with tasks, or because tasks in the template don’t count as a task being added. Either way, it doesn’t work.

If you pre-add them to another project though, the Task is added to this project trigger works for that other project.

You then have the rule do the thing you want, and - assuming this isn’t the start of a process workflow - you might want to keep the project clean by closing with a Remove task from the project action

I’m hoping this gives you some new options for setting up advanced workflows.

Jan-Rienk - Asana Expert @ Improving Every Day

:information_source: Related:

10 Likes

I am not sure I knew, thanks!

1 Like

Another useful post, @Jan-Rienk :+1:

Within the template editor, you can multi-select (all) tasks and add them to a project in bulk, just like you would if they were in a project.

Great tip!

2 Likes

I’m not sure how I missed that.

Corrected it, thnx!

1 Like

Very clever!! I like the theory that the rules are added to a template after the tasks have already populated.

Rather than triggering when they are added to this project, you make them trigger in that project. I look forward to experimenting with this! Lots of automation-only projects hiding my team’s All Work list.

I think we are going to need new filter/sort/section controls within the Team pages to keep things organized.

2 Likes

Are you sure? We just tried and it doesn’t work.

@Bastien_Siebman that’s odd.

I sure tested it, knowing this was the linchpin for the entire article.

I’ll walk you through how I tested:

Rule in “Project with rule(s)”:

Created project from template:

Rule execution history:

Activity log in task:

Can you test this exact scenario and circle back?

1 Like

Apologies, we didn’t test properly, your screenshots helped! It works!!!

2 Likes

Glad to hear. :slight_smile:

Hi Jan-Rienk :slight_smile:

I have a question, maybe you (and others) could brainstorm with me to find a workaround.
I did this exact same thing, though the rule I want to run is renaming the initially added tasks by adding the newly converted project’s name at the end of each task.

(I know I could do it with AI Studio, but I’d like to find a workaround instead).

I thought setting it up, as shown in the attached image, would be fine.

However, it appears that steps 3-8 are executed simultaneously, so the rule set up in the project template doesn’t run, as it doesn’t detect any change in the due date.

If I could add some delay, it’d work great, but I couldn’t find a way.

Could anyone suggest a solution here? It’s not a crucial step, but it’d be super nice. In the process we’re discussing, we have numerous projects with multiple tasks created each month, so differentiating between the tasks solely by their names would be helpful.

(And because it’s a lot of tasks, I’m not inclined to use AI Studio for it because most likely it’d consume a tremendous amount of credits.)

Thanks a lot!

Welcome to the forum @zajormita :slight_smile:

I’m not sure if I understand you correctly, but if you want to have rules execute in sequence then I’d suggest having the last action of the preceding rule be the trigger for the next rule. Most straightforward would be to flip a custom field to indicate which rule to run next, and clear it once the last rule has run.

Does that answer your question?

If not, timer fields may provide a solution, but they I have found them to be a bit dodgy to trigger rules: Subject: Automating Feedback Reminders – Looking for Tips to Refine My Workflow