"Task is moved to a section" triggers even if task is moved outside of a section

English Forum Product Feedback
1

Hi,

If you create a rule with this trigger

CleanShot 2026-03-04 at 15.55.00
CleanShot 2026-03-04 at 15.55.00392×131 3.89 KB

you’ll notice that if fires if:

  • the task is placed in the project, outside of any section
  • the task is moved outside of a section

To me, this is a bug. And because a rule in a bundle doesn’t have the condition “section is not undefined” I am stuck :sweat_smile:

1 Like
2

@Joanna_Colgan I hope this is a bug, but I am afraid Asana will consider this to be expected behaviour…

3

Voted! Regardless whether it’s classified one way or another, the root cause is that implementing minimal options may be a slight UI simplicity improvement but more importantly is a complete dead end for your workflow when you need it.

Like coding defensively, it’s good to design defensively.

Thanks,

Larry

1 Like
4

@Joanna_Colgan were you able to raise this one with the team?

5

Hey @Bastien_Siebman , sorry, yes! I actually didn’t have to flag it as it’s already been reported by someone else. It’s a part of a bigger bug which is being investigated. We are hoping to see some solution by the end of April.

6

Hi,

Any news on that bug? Thanks

7

@Stefan_Kirilov I wanted to double check if that has been seen by your team. Thanks