We use repeating tasks to manage regular pieces of work and have set up custom fields to allow us to monitor the progress. However, when we mark the task as complete the repeating task is created with the same field option as at the time that it is marked complete.
I would love to see a new rule option that allowed a field (or column/section etc) on a newly created repeating task to be set.
Has anyone got a similar problem?
Sounds like a great idea @Rod_Petrie, hopefully this is something we can implement in the future. While I canāt promise anything at this stage, Iāve made a task to our Product team to take it onboard for future updates 
It would be great if you could set options for a repeating task that tell you what the fields should default to when the original task is complete.
I have tasks that I want to keep the same description and assignee, but nothing else. I also have tasks that I want to completely reset ā including removing the assignee because itās a new owner each week.
Yes! Hitting this particular pain point at the moment. As Justine suggested, would be great to be able to decide the default by field/tag (clear it, keep it the same, or set it to a given value).
Weād also benefit from this. We have recurring tasks that are part of a weekly sprint and it would be great to be able to automate incrementing the Sprint field by 1 on the newly created task. Current process is to close the task, wait for the new task to be created, find the new task, update the Sprint field manually.
I, too, have a repeating task that falls into different sprints. It would be great to have a field or two that doesnāt repeat but, instead, gets set by board rules on the newly created task. I have to manually change the sprint on each repeating task.
When a task has a recurring due date, the new task is created by duplicating the existing task, but with a new due date assigned to it. For the most parts, this works. However, this new state is a task that has not been worked on yet, so the status should not be the same as the previous task, which has just been completed. There is currently no way of changing the Status or Section of the new task through workflow automation, because no automation applies to a duplicated task.
The follow two solutions would get over the problem:
a) When setting the recurring due date, allow the user to choose if they want the Status and / or Section to reset and to what.
b) There should be sets of workflow automation that applies to duplicated tasks or have duplicated tasks recognised as new tasks added to the Section / Project so that existing workflow automation could apply.
@JingaLingaLin 
Welcome to the community!
I 
% agree with you on this. Remember to add your own vote.
Agreed! also wild that we still have no progress on Recurring Tasks on certain day/week of month not the actual day after YEARS of people asking for this feature
Hi all
Meanwhile we get that feature on the roadmap, I may have found a workaround using Customized rules (Business plan or above).
Please see my idea there Recurring Tasks status change - #3 by Arthur_BEGOU
FYI on this topicā¦
The āTask is newly addedā rule trigger in our Flowsana integrationās rules will fire when a new instance of a recurring task is created, so that trigger can be used to automate actions on a new instance of a recurring task.
Is there any update on this task - been trying all sorts of rules to get a duplicated task to move section!
Iām wondering if there are any updates on improvements for repeating tasks, specifically related to how custom fields behave. Currently, when a repeating task is marked complete, the custom Status field copies its value to the new task. This results in the new task being set to Done (or other status value that is no longer to do) which isnāt ideal.
It would be great to have more control over thisāsuch as the ability to:
ā¢ Select which fields to copy.
ā¢ Specify a default value for certain fields.
ā¢ Leave certain fields blank in the new task.
Looking forward to any updates on this! 
I agree with everyone here. This is a flaw that needs to be corrected. Users should not have to jump through advanced rules to make this happen. The average user will struggle.
When will this be in development?
Hi Jason,
Iām afraid Asana doesnāt have a public roadmap so we donāt know about potential features until they roll out.
@Rod_Petrie I think Enable Recurring Tasks to Trigger Rules - when implemented - would also solve this problem. The only thing youād need to add then is a way for the rule to know which tasks are recurring. This could be done with a custom field, or by creating a project to house recurring all recurring tasks.