We’re currently having an issue where when we’re working through a task with multiple subtasks - the main task is assigned to someone and when we’re assigning the subtasks - it keeps changing them to the main task assignee - even though there’s no rule in place and will override the assignee we’re trying to put in.
Is there a way around this? Finding it really frustrating!
Hi @Kim_Luscombe , that sounds odd. It could be a rule that is being triggered from another project which the tasks might be also added to. You may or may not be able to see that additional project, depending on whether you have access to it or not. Might be worth asking your colleagues / team members if this could be the case.
Otherwise, feel free to post some screenshots, which may help me and others help you 
Thanks Richard! They’re all new projects, which I’ve got ownership over so there wouldn’t be the chance of them being in other projects.
I’ll get the team to replicate this so we can post some screenshots/video snippets in!
Added two screenshots - the first where the second approval task is assigned to KL (me) and the second shows that it is now assigned to ST - it’s automatically changing every single subtask to ST when there’s nothing in place that is causing this.
Your screenshots show that not only is the assignee changing but so is the task type–from regular task to approval task.
I agree that a rule is changing this, but maybe if you really are sure it’s not an Asana rule, then perhaps it’s a Flowsana rule? (@Phil_Seeman)
Thanks,
Larry
Or perhaps there is a Rule in KL’s My tasks?
If you are using Flowsana, do check to see if any Flowsana rules are involved.
Also, look at the activity history for the subtask after it gets changed and see if there are any clues there. (Feel free to post screenshots of that history for us to review if appropriate.)
Thanks for all your responses!
We’re not using Flowsana.
It’s correct that we have a few approval tasks as subtasks - so these aren’t being changed.
Regarding rules, there aren’t any that could be triggering this - the only rules in KL my tasks is when a subtask is marked as complete it’s moved to a complete section and when the due date is approaching it’s moved into a ‘to do today’ section. This is the same for all the team, who are also experiencing the same issue.
After the unwanted change(s) occurs, what does the activity history show?
@Kim_Luscombe Did you ever figure this out? this is happening to us too and I’m not sure what’s going on. It’s getting triggered every time anything changes on the subtask.
Scroll down to the top of comments on that specific (sub)task and select all activity to see who/what changed it
Are you perhaps adding all subtasks to another project which contains rules that are triggering things?
@Jan-Rienk I looked at the activity, it says that the main task assignee changed it. I know she’s not waking up at 1 AM everyday to reassign a bunch of subtasks. We’ve also had it happen to tasks where the task was assigned to me and the subtask assigned to other people. It seems to mainly happening when a particular custom field value is changed.
@Richard_Sather We are not adding subtasks to any projects, and I looked through our Asana and Flowsana rules, we have no rules in any project with a change assignee action, so I’m not sure why the assignee is even changing.
That sounds like a bug.
@Forum-team could this be related to this critical bug?
I know it’s not the same, but it also seems like unexpected rule behaviour.
@Kriti5 if it isn’t related, best course of action would be to report it to support.
Support is having a bit of a challenging time a.t.m., so if you have trouble reaching them through the help center see this topic on how best to reach them.
Hi @Jan-Rienk Thank you for bringing this one to our attention!
@Kriti5 First of all I am sorry to hear that you are experiencing this issue. Since this seems to be different from the general issue, I agree with Jan-Rienk’s suggestion, it would be best to contact our customer service.
Sounds like the owner of the rule has some “due date approaching” rules set up in their My Tasks that are triggering this in the early hours of the morning. They need to change the rule to only run on tasks and not tasks & subtasks.
This happened to me too and I figured out the solution because it only happened on subtasks (assigned to others or empty) that sit underneath a task (assigned to me).
It seems like a big oversight that this is happening. Rules in My Tasks should only run on tasks that are assigned to yourself. You can’t even add a condition for it to check that the assignee is yourself.
Just getting back around to looking at this. I didn’t have any Asana rules set up at all, only Flowsana rules.
I have some more details – this only happened when both me and a colleague set up Flowsana rules in our “My Tasks” projects that used the same custom field. It only got triggered when that specific custom field was changed (as far as I could tell), or when the Flowsana rule on that custom field was run. She deleted her Flowsana rule, and this hasn’t been happening anymore.
I’m assuming this is a Flowsana bug, so it probably doesn’t make sense to follow up with Asana customer service, right?
Hi Kriti,
FYI we’re happy to look into it re. Flowsana if you want to submit a support ticket to us.
