Rule keeps moving task back to initial section

English Forum Critical Bugs Closed
1

image
image1271×410 16.9 KB

I have created a rule to un-assign when moved into a column.
However when I assign myself to a task that is already in that column, it will un-assign me. This never used to happen.

2

Hi @Molly_Cleary , welcome to the forum :wave:

It sounds like this might be a new rule that might be causing this. The rule in your screenshot would not trigger based on the conditions you describe because the trigger is not when you change the assignee (you). Does it only happen to tasks in the ‘Needs checking’ section? Does it also clear the due date? If not, then it is another rule that is running.

Could you open the task details pane and scroll down and choose All activity (instead of Comments), click on Show all previous updates and check the log by hovering your mouse over :zap: Asana to see the name of the rule that ran the action that unassigned you.

Note, this rule may not be within your project; it could be in another project that the task is also added to, or perhaps in your My tasks.

Have a look and let me know!

3

I have set up a rule which adds a task to another project (project E) when it reaches a certain section in the first project (project O). This works fine. And until today I was able to move the task along the sections of project E no problem at all. However, today this rule keeps moving the task back to the initial landing section of project E. Any ideas?

1 Like
4

Ok so I have discovered the reason for the new behaviour is that I added a new section to Project E. I have deleted it and the rule does not get triggered when I move a task in the project now. But any idea why? And how do I modify the project without creating this behaviour?

5

Hi @Claire_Wightman1 , welcome to the forum :wave:

Are you able to post some screenshots of your rule in the builder/editor window so we could have a look and help you out?

You may want to check for rules in both projects O and E that would trigger on tasks that belong in both projects.

6

I am having the same issue today. Unlike Claire, I haven’t added any new sections to either of the projects nor changed any of the rule settings. It was working perfectly fine up until this afternoon, now all tasks are automatically going back into the first section of the project regardless of it being moved. Has something changed on Asana’s end that is tampering with the rules running properly?

7

Hi, thanks for replying!
I did this and it said the rule was coming from the rule I screenshotted in my post (so another rule isn’t causing it). This wasn’t happening till a few days ago and nothing had been changed.

8

Hi,

I was trying to find some topics on this, but can’t really notice anything.
Are we alone in having problems with Asana rules triggering in wrong way since 24 hours? We had to pause bunch of scripts/rules, as all workflow was corrupt.

Thanks.

9

I am having the same problem. It adds to the additional project (Project B) but it auto assigns a section, now we can’t move the task out of that section within project B, because it keeps moving it back.
I have a rule in project B that puts all new tasks in a specific section when added to the project, but this ‘add to additional project’ rule seems to bypass/overrule that one.

10

Here is a screenshot of the rule. If only you could remove the ‘choose a column/section’ dropdown it would run perfectly.

image
image1689×372 32.3 KB

11

Hi @Molly_Cleary , this is strange. Other people are also reporting strange behaviour with their rules, here too:

Should we perhaps merge under one thread?

Can you also try this:
https://forum.asana.com/t/asana-rules-malfunction-since-24h/949595/3?u=richard_sather

12

Hi @Forum-team , seems like several people in this thread are reporting strange behaviour with rules, including these thread, too.

Could you kindly review and if deemed a bug, escalate to the product team?
Thanks!

13

We’re having the problem as well that rules triggered by “Task is moved to a section” are triggered if tasks are moved in other projects than the one where the rule is defined in.

Here is a reproducer:

  • Add project “Test 1” with sections “Foo” and “Bar”
  • Add project “Test 2” with sections “Foo” and “Bar”
  • Add task that lives in section “Foo” of both projects
  • Add rule to “Test 2” that adds a comment “Moved to Foo in Test 2!” whenever a task is moved to section “Foo”
  • Move the task to “Bar” in “Test 1”
  • The comment “Moved to Foo in Test 2!” is added, even though the task wasn’t moved there
14

Hi everyone,

Thank you for bringing this up, and I’m sorry you’re having trouble with the project rules.

We’ll look into it and escalate to the product team if needed.

Appreciate you flagging this, @Richard_Sather!

Marking this post as a solution to provide visibility, but we will keep you updated.

2 Likes
15

Hi,

I was trying to find some topics on this, but can’t really notice anything.
Are we alone in having problems with Asana rules triggering in wrong way since 24 hours? We had to pause bunch of scripts/rules, as all workflow was corrupt.

Thanks.

16

My organization is having problems as well. A rule is in place to add a task to a certain section in project “B” when moved to a certain section in project “A”. The rule is basically locking the task in the “recently added” section of project “A”. Every time an attempt is made to move the task to a different section within project “A”, the rule kicks it back to the “recently added” section. In short, the ability to move tasks within a project has been eliminated by the rule whereas, just 2 days ago movement was possible in spite of the rule.

1 Like
17

@Adrian3 , @Joseph_Rubenacker , someone has reported this here:

Could you check that it might be that “Allow this rule to be triggered by other rules” was enabled?

18

Hi,

I checked problematic behaviour and it’s not related to this setting, as we had it turned on.

Long story short:

Section A → rule A1 triggers when moved to seection A1, sets field F to A.
Section B → rule B1 triggers when moved to section B1, sets field F to B.

Rule A2 triggers when field F set to A and moves to section A.
Rule B2 triggers when field F set to B and move to section B.

So basically field and section is connected.

Now we have following situation to happen.

Task X is in section A, field is set to A.
User changed F to B.
Asana triggered B2 rule and moved to section B.
Asana triggered B1 rule, as task ended up in section B.
Asana triggered A1 rule, which was totally wrong, as task was no longer in that section, which resulted to task get back to previous state


So it seems that SECTION rule trigger failed in our case.

19

@Adrian3 , other are reporting similar issues with conditions using Sections and I’ve flagged this already to the @Forum-team.

In the meantime, you could use the Group button in List or Board view and select your custom field ‘F’.

You would then have to manually clean up after this issue is resolved. Or you could pause/delete all rules that connect sections to you field, then delete all sections and instead use the Group button. But take care, as I’m not familiar with all the nuances of your project.

2 Likes
20

I have another example, which is WAY easier.
Project A has section rule, which removes from this project.
Project B has section rule, which add task to project A.

Task does not change section in B project, but rule is triggered when section is changed in A project. Seems like section trigger is broken
 to trigger every project task is, NOT the one which actually had section changed.

We can show really easy example to some DEV team


1 Like