Remove from Project Rule action

I would like to be able to remove a task from a specific project based on a trigger (i.e. - task completion).

9 Likes

Hi @Jeff_Kassel, thanks for providing this feedback!

While it’s not possible to remove a task from a project without adding it to another with Rules, hopefully this is something our Product team can implement in the future.

I’ll keep you posted and let you know if I have any updates :slight_smile:

@Jeff_Kassel

Whilst not able to be done in Asana, there are integration tools like Integromat, Flowsana and Zapier that can do this.

Regards

Jason.

1 Like

I would also like this ability. We have scenarios where we create an ‘external’ project which contains a subset of the tasks from the main project. We do this to share the tasks of the project that require external (guest) feedback and completion. This way those external sources can view their portion of the project easily in Asana. It is helpful to use a rule to allow our internal team to quickly/easily add tasks to this external project. However, without and ‘action’ to remove from a project, we can’t setup a rule to do the opposite, which then means internal staff need to learn two things to accomplish one primary goal: sharing/unsharing tasks.

2 Likes

Would love to see this as an option in the future in the rule building applet.

Hello @Heather_Davis welcome to the Asana Community Forum :wave:

I have merged your post into an existing product feedback request thread :slight_smile:
Don‘t forget upvoting.

1 Like

I am trying to find a way to remove all projects, once I move that tasking to a different project under the same team. The taskings is started by the management but then moved to employees but with an additional project added for that set of employees. Once completed the managers must manual remove the second project from the tasking. This takes time since the tasking my be assigned to multiple projects before being complete. Once verified compete the tasking is moved to completed tasking project that is held for one year (To reference back if needed). I am looking for a way to remove all projects once I move that tasking to the completed project. Any help is welcomed.

Welcome to the Asana Forum :slight_smile:

I have merged your post with the already existing request which has more votes. You can upvote that request; the more upvotes, the higher the possibility that the feature request gets prioritised.

Cheers,
Rosario

1 Like

@Phil_Seeman - can you shed some light as to whether this is possible in Flowsana? I’m not seeing an option to remove the task from a project.

I am aware and have been using the “move to another project” rule, but once the task is in two projects after an “add to another project” action, the moving doesn’t remove it from the source project.

@Jorge-wms,

Try the Flowsana “Move to project” rule action - it should work differently than the Asana one. The Flowsana rule action should remove it from the source project even if it already exists in the target (i.e. the “move to”) project.

Hi @Phil_Seeman , great work with Flowsana!

Yes, Asana seems to do the following in the below scenarios:

Scenario 1:

  1. Task X is in Project A.
  2. Rule ‘Move task to another project’, to Project B.
  3. Task X is removed from Project A and appears in Project B only.
    Great, but…

Scenario 2:

  1. Task X is multi-homed in Project A & C.
  2. Rule ‘Move task to another project’, to Project B.
  3. Task X is removed from Project A and appears in Project B but still appears in Project C also :confused:

So in Flowsana, is it possible to do the following?:

  1. Task X is multi-homed in Project A & C.
  2. Rule ‘Move task to another project’, to Project B.
  3. Task X is removed from Project A & C (all projects it is multi-homed) and appears in Project B only…?

@Richard_Sather,

No, that’s not currently possible (as you discovered). That would probably require adding a real “remove from project” rule action. It’s an interesting use case and something for us to think about for the future.

2 Likes

Hi. Flowsana is not an option for us currently. Would be great if this could be added to the functionality within Asana (I actually only need this functionality, because other functionality – i.e. multiple due-dates – is not available…)
Thank you!

I would support that development Phil. Funny enough the workaround I am developing to deal with “convert to subtask” pulling tasks out of the home I have them in, is multi homing.

However, when a process is completed for the year I will need to remove several tasks from 2 of the 3 projects they will be linked to so this would be helpful

2 Likes

Hey there!

I’m looking for something similar. We have multiple projects but I have a rule in each project that automatically moves tasks from that project to another project one assigned to a particular staff. The other project services as a repository for all tasks assigned to a particular department.

Once it’s in the consolidated project and the task gets assigned to someone else outside of that department, I don’t see any rule that removes the tasks from the consolidated project.

If someone out there does the same thing, consolidating tasks into one project, how do you usually handle this use case?

Thank you!

Hi Karl,

I have a similar issue in my organization and if Asana would allow UNASSIGN AS A TRIGGER and/or REMOVE FROM PROJECT without selecting another one, that would just fix everything.

In the meantime here is what I do but it’s tedious :

  1. I have one project per TEAM

  2. I have one project for each TEAM MEMBER

  3. In the TEAM project, I create a rule that says:
    Trigger: When added to this project AND assigned to X → move to the assignee (X) section. Action: MOVE (not adds) the task to the TEAM MEMBER project.

  4. In each TEAM MEMBER project, I create one rule that says:
    Trigger: If the assignee change to A,B,C,D… (all assignees possible for that team) Note: Select when ANY of those triggers happen)
    Action: MOVE task to the TEAM PROJECT in the section “tasks to check or unassigned or any that is not an assignee section”

I feel like you can replicate that concept for any flow, playing with custom fields instead of assignees, status or project stages for example.

1 Like

Hi all,

I want to great a meeting agenda project, that is auto populated and ultimately, depopulated,

In this case, I have a project where the initial status is ‘In triage’. I want this to populate a ‘weekly meeting’ project in the ‘Tasks in triage’ section. Easy done.

However, when we change from in triage to any other status, i want the tasks to be removed from the agenda (as we will have reviewed it). Throughout this process, i don’t want the tasks removed from the other project (eg, move to one project project, moved back to the other). I also want the rule to run on any status change (so not when it’s changed to specific one).

Is any of this possible?

Welcome to the Asana Community Forum👋

I have merged your post into an existing feedback request thread.
Maybe you consider just moving the task in the existing project to a separate stage that is only used to store already addressed tasks?

I would like to add an upvote here. I am starting to utilize secondary projects for tasks. I have a main project and then have created a weekly to-do list project that I’m assigning a task to also. I would like to be able to set a rule that when I complete on one project it removes it from the other project.

1 Like

Thought I would put my user case here.

I am trying to run a “zero inbox” project/board that I use for delegating and revising tasks. With the aim to move them around to places they need to be.

Having a rule to allow it to be removed from the board that I am managing would just make it more efficient.