How to create the rule moving task from one project to another without creating its copy

[Sobru]

Hello Asana community,

I’m looking for a way of creating two automatic rules:

1. Moving task from one project to another without creating its copy. The rule must be triggered by age of task since it was completed. This is meant to create some kind of automatic archive.

2. Copying task from one project to another but without making them interdependent. I would like to keep this task completed in one project and create copy “to do” in another one. So far, I just found option to make the copy, but any change made on the copy has reflection on the base project and the other way around.

Thanks for your support in advance,
Adrian

[Jerod_Hillard]

Hello @Sobru and welcome to the forum!

@Sobru

Moving task from one project to another without creating its copy. The rule must be triggered by age of task since it was completed

Currently, Rules don’t remove tasks from one project and assign them to another. I assume that is what you meant here but perhaps you are hoping to multi-home the task to another project which wouldn’t create a copy but instead allow the task to exist in two places. Rules DO have this ability today. You just aren’t able to remove a project from a task through Rules. Also, there isn’t an trigger for the age of a task (whether the age is defined by “time since completion” or “time past due”). Perhaps these are things that Flowsana can help with. Can it @Phil_Seeman?

@Sobru

Copying task from one project to another but without making them interdependent. I would like to keep this task completed in one project and create copy “to do” in another one. So far, I just found option to make the copy, but any change made on the copy has reflection on the base project and the other way around.

I think what you are describing here is the multi-home feature I mention above - where the task isn’t copied as much as it lives in two places. When you multi-home, tasks are interdependent as they are actually the same object in Asana. If you want to be able to complete one task separately from another then you need to create a duplicate task which unfortunately is also an action that isn’t supported by Rules. Again, maybe Flowsana can help with that @Phil_Seeman?

[Phil_Seeman]

Hi @Sobru,

Flowsana can get you part of the way to your goals but not all the way.

@Sobru

Moving task from one project to another without creating its copy.

Flowsana can do this; unlike Asana, Flowsana’s rules have a “move to project” action.

@Sobru

The rule must be triggered by age of task since it was completed

Flowsana does have pretty comprehensive date-based rule triggers, but they look at a task’s start or due date, not its completion date. It’s an interesting idea I hadn’t thought of before to include completion date as a possible rule trigger. I’ll give that some thought and might add it to Flowsana.

@Sobru

Copying task from one project to another but without making them interdependent.

Like Asana, Flowsana has no facility to do that via automation. You might be able to use Zapier to do it. It wouldn’t be able to copy ALL elements of a task, but it might be possible to get what you want in terms, not 100% sure.