Recurring Tasks in Sections

English Forum Tips and Tricks
1

Hello, I have a series of tasks grouped in different sections that have a date set to re-occur. My teams wants there to be a rule that when the due date is approaching, the task(s) move up to a section higher in the project to notify them that they need to review it. Then, they would complete the task and the next version of that task would MOVE back to it’s original section until its next due date.

For example:
Task 1 is set to recurring in Section A and is coming due.
Task 1 in Section A moves up to Section B for review.
Task 1 is reviewed and marked complete.
New Recurring Version of Task 1 is added and returns to Section A.

2

Hi @AmyPeters,

You could use a Custom Field to store “Home Section”

  1. Create a single-select custom field (e.g. “Task Origin”) with values like “Section A”.
  2. Assign the correct value to each recurring task.
  3. Add a Rule:
  • Trigger: Task is added to project (new recurring task appears).
  • Condition: If “Task Origin” = “Section A”.
  • Action: Move to Section A.
2 Likes
3

Thank you for the response. I replicated this rule but when I mark “complete” on the recurring task set with the custom field to call it back to its original section, it still seems to reappear only in the section from where it was completed. Let me know if you have any thoughts as to why - perhaps this rule doesn’t work if task is recurring?

4

Hi @AmyPeters

My apologies, I thought for sure I had been able to do this before… I looked back through and it appears you are correct, it will not trigger from a recurring task. It looks like the workaround that I used was based on completion of the subtasks.

  • Trigger: Subtask completion has changed & all subtasks are marked complete
  • Condition: If “Task Origin” = “Section A”.
  • Action: Move to Section A.
  • Action: Mark Task as “Complete”.

I have tested this and it will cause the new task to generate in the appropriate section, however if someone simply marks the task complete, it does not move.

5

Asana rules don’t fire on recurring tasks. (Our Flowsana rules, do, though. :wink:)

1 Like
6

Thank you both! It is good to at least confirm I am not missing something easy to fix this. I’ll consider the subtask route. Considered Flowsana as well, Phil, so thank you! :slight_smile: