I set up an issue in my master project, let’s call it ‘project A’ that says “When task is moved to section X, add task to additional project B.” There’s another rule for section X in project A that says, “when task is moved to section X, assign it to Jim.” It was working just fine until yesterday when the project A rules started triggering throughout project B. When I try to move a task to another section in project B, the rule “when task is moved to section X, add task to additional project B” triggers and moves the task back to the top section in project B. Additionally, when I change the assignee in project B, the project A rule “when task is moved to section X, assign to Jim” triggers and Jim get’s assigned. Any idea what’s going on here? It’s not just project B that’s affected, its all projects that receive tasks from project A.