Multi Homing Tasks

English Forum Ask the Community
, ,
1

Hi everyone,

I’m looking for advice on the best way to structure projects and automations for annual work.

I have a central Requests project where every incoming marketing request is submitted. I use rules so that when a request reaches a certain status, it’s automatically added (multi-homed) to another project for tracking.

The challenge is that the destination projects are year-specific (for example, Marketing 2026, Events 2026, etc.). Since a new project is created each year, it seems like I’d have to go through and update every automation rule every January to point to the new project.

On top of that, these yearly projects contain recurring work (weekly, monthly, quarterly, and annual tasks). Throughout the year, I often need to add new recurring tasks, refine workflows, or make process improvements. Right now, those changes have to be made directly in the active project, which isn’t ideal.

What I’d really like is something like this:

  • A yearly project template that acts as the source of truth and can be continually improved.
  • An active yearly project that’s generated from that template without requiring me to manually recreate or revise everything.
  • Rules from my Requests project that automatically add tasks to the correct yearly project without needing to be edited every year.
  • A workflow that’s scalable and requires as little annual maintenance as possible.

I’m wondering if there’s a better way to structure this. Is there a way to avoid updating automation rules every year when the destination project changes? Has anyone found a good solution using templates, bundles, portfolios, or another Asana feature?

I’d love to hear how others manage annual projects and recurring work while keeping automations easy to maintain.

Thanks in advance!

2

Hi @Angela_Chen , unless there is a very good reason, I would recommend avoiding yearly projects and instead opt for perpetual projects so you only maintain one version.

If you want to view tasks by year, you could create view tabs, filtering by due date or creation date, whatever works. That should avoid the need for creating separate yearly projects.

If however you need to have yearly projects, then a scalable solution, which requires low maintenance, would be to leverage the Bundles feature, which is however exclusive to Enterprise. You could add a bundle (or multiple Bundles) to your project template and all yearly projects so that you could then ‘push’ any changes to rules, fields, sections or task templates, to all those projects or project templates, in one click!

Then again, adjusting your rules once a year could be considered low maintenance, depending on the amount of projects you have.

3

Welcome, @Angela_Chen,

I’d like to propose an alternative approach that does not require Bundles and may be valuable to some over @Richard_Sather’s solution, with which it shares the notion of an evergreen project:

Thanks,

Larry