Recurring Tasks status change

Hi All,

I wanted to your help on a query I had. I had created a recurring task once a week. One of the columns fields also I have created was the status - “not started, overdue, completed and in progress”.

Once I complete this week’s task by ticking on the complete button as well as changing the column status field to complete, the system automatically creates a new task for next week but with the status field as ‘complete’ instead of ‘not started’. How do I fix this issue? Is there a rule or option I can use?

1 Like

Hi @Mohammad_Nimer , welcome to the forum :wave:

What you are experiencing with recurring tasks is expected behaviour, since it actual duplicate the task, along with the values of any custom fields.

Unfortunately it is not possible to overcome this issue by using a rule because the recurring tasks is not treated as a new task added to the project. So both triggers ‘task is moved to a section’ or ‘task is added to this project’ have no effect for this case, in order to action the status, for example, to rest back to ‘Not started’.

You can vote for this feature in the following threads which are slightly different:

Hi Mohammed,

Maybe an idea for a workaround with rules (@Richard_Sather I’m curious what you think :eyes:)

If you have the chance to use the Asana Business plan (or above), you can benefit from the fantastic Customized Rules. With that feature, you could try to re-create a basic recurring task behavior, without using the actual recurring task features. This will allow you to automatically change your Custom Field for newly created tasks.

The ingredients

  • 1- A section dedicated to those recurring tasks (we will use the section as a trigger for the rule)

  • 2- An advanced rule that will create a new task every time the previous one is completed, every 7 days (steps 1,2,3,4,5) - see screenshot

Next screenshot is a zoom on the “View all fields” (5)
then select the right section for the new task (6)
then define the field “Status” to “Not Started” (7)

And the final result in a .gif


Ooooh that’s very clever @Arthur_BEGOU !

The only drawback is that you are limited for options of when the task will recur, but other than that, excellent suggestion and very nicely presented, as always! :+1:

1 Like

One drawback, which will be a benefit for some, is that a newly created task will be created by the rule and won’t be duplicated from the previous task. So if you task “evolves”, the next ones won’t get those “evolutions”.

Well done @Arthur_BEGOU !


@Richard_Sather and @Bastien_Siebman, FYI both of those drawbacks can pretty much be eliminated if one uses the Flowsana “Add tasks” rule action instead of the Asana “Create a task” one. :wink:

We should create an automatic disclaimer “Most requests are covered by Flowsana, please check it out” :rofl:


This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.