This is happening across our team. We all implemented a rule in our individual My Task pages that when the Due Date was approaching, it would move the task to a “Due soon” section. Now when activated, it’s re-assigning whoever’s assigned to a subtask being moved to whoever owns the main task.
It seems like this was a known bug for a while that was triggered by the “Run on subtasks” toggle in the Rule being turned on, but that toggle is turned off automatically now on My Task rules and it’s still happening.
FWIW, I just tried to reproduce this and couldn’t; it behaved as expected for me, not changing the subtask’s assignee.
I didn’t use “Due date is approaching” but instead “When task is no longer blocked” as my trigger, so it’s not identical to your case, but similar.
Did you check the specific rule’s setting for Runs on subtasks? It’s set rule-by-rule and must be toggled off for the rule you’re testing to ensure the subtask behavior is avoided.
this is happening to us as well. It is changing the assignee when something is completed etc. if the rules are the simple “when task is completed move to section” or “when task is due today move to section due today”.
this task was originally assigned to me, when i marked it complete it was changed to the other person because on their My Tasks they had a rule ““when task is completed move to section”
Hi @Lindsay_Mancuso thanks for flagging this, I know how frustrating it is when My Tasks rules affect items you didn’t intend.
Quick context: in My Tasks, any subtask assigned to you will appear like a normal task. So if a rule condition is broad enough, it can unintentionally act on those subtasks as well.
A few quick checks that usually help resolve this:
In My Tasks, open your rules and review whether there’s any action that “reassigns” or “changes assignee.”
Add a narrowing condition like “Project is …” so the rule only applies to tasks from specific projects. This is the most reliable way to prevent unrelated subtasks from being included.
If there are project-level rules that also reassign tasks, check whether those subtasks are multihomed into those projects, as that can also trigger unexpected behavior.
As a temporary workaround, disable the specific reassign rule, confirm the behavior stops, then re-enable it with tighter conditions.
If possible, could you share:
A screenshot of the exact rule in My Tasks (trigger, conditions, actions)
One example task link where this happened and the approximate time
Whether that subtask is also in a project that has its own rules
Something similar is happening to me with tasks, not subtasks. A task is assigned to someone else but a rule in my own My Tasks is reassigning it to me based on the approaching due date and moving it into a section. I checked to make sure none of my “due date is approaching” rules included a reassignment condition. But when I went to specify the condition that they should only impact tasks in My Tasks, that didn’t come up as an option, since it’s not actually a project. How do I do that?
(Related side note: The due-date based rules that I have in My Tasks are not consistently moving tasks into the right sections. They’re supposed to run at midnight but tasks will sit in the wrong section for days after the due date changes.)
You may also need to check the My Tasks rules that have a “Do this” to move the task to another My Tasks section. Asana gets overzealous trying to please, so if that rule triggers on a task not assigned to you, it will honor that request by first reassigning to you (because it can’t execute that section move without that). So you won’t see that in your rule action.
Including the condition that you are the Assignee.
These rules must match exactly, just after midnight, for the day you specify; they won’t match after that day passes.
Hi Larry - I did not already have a condition that the tasks are assigned to me because I assumed that if the task was in My Tasks (where the rule is applied) that it would be assigned to me.
However, I went to add the condition but Assignee is not an available option. This kind of confirms that it should already only be running on tasks assigned to me. The only other relevant condition is “task is in any of these projects” but My Tasks isn’t a real project, so it doesn’t come up. How are you setting these conditions?
