In the rule builder, I would love to see the project field for subtasks/tasks created by a rule to have a variable option for same project as the rule is seeded from.
I have a template (now in a bundle) for a project I create monthly. Two of the rules create subtasks that I want to add to sections further down on the monthly project being created by the template.
Currently, this means that every month, when I use the template, I have to go into these rules and add the project created by the template to the “create subtask” subtask fields.
It also means I have to leave these two rules out of the bundle for the template and monthly projects because the project field varies.
If the field was variable, there would be much less manual work, and no concern of missing a subtask because this step was missed when the monthly project was created. I could also use a bundle for the template and monthly projects in their entirety to ensure other parts of the rule are consistently updated when I need to make tweaks.
Example - I am editing a rule on the 2025-11 November monthly project:
While it would be a significant one-time change, perhaps you or other readers here might consider this approach as a workaround until/if this feature is added by Asana:
I love evergreen projects! We do use an evergreen project for intake and another for deployment. I do worry about the volume growth over time, but I don’t think it’s a big deal to end a project at the end of some year and start a new evergreen project if the data becomes unmanageable for reporting or any other purpose.
I like using a mix of evergreen projects and monthly projects to manage work. Monthly projects are cleaner for reporting and metrics, but we have have made it work with evergreen projects as well. So far, the limitations are worth the trade off, but it is definitely something we should reassess intermittently.
