I have a bundle that has sections and a set of rules that take care of synchronizing columns and a custom field mapping to those columns across several projects a task might be multi-homed to. One of these rules seems to not execute in a particular project that has this bundle.
Within the bundle there are two very similar rules. The first is triggered by a custom field change and moves the task to the appropriate section based on that field’s value. The second is triggered by a section change and sets the custom field to the appropriate value. I’ve needed to separate these two rules because there are other conditions in the rule logic and there is no way to group conditions at them moment, which is outside the issue but I mention in case consolidating the rules is offered as a solution. Both rules work perfectly across the 2 out of the 3 projects I’m multi-homing. In 1 project, the second rule (trigger on section change) does not appear to execute. The first rule works fine in all 3 projects. Is there any reason why the same rule in a bundle shared across several projects would not fire in just one of those projects?
Image of the rule that does not work in 1/3 projects:
Image of the rule that works in all 3:
This may be a red herring, but there seems to be other syncing issues of the rules themselves. In the below screenshot, the projects Trading Roadmap[TR] and Trading Ad-hoc all share the same rule bundle as the project I took the screenshot from. I expect to see the rule Sync state and Kanban when completed from the current project as well as the two others, but there isn’t an entry from Trading Ad-hoc for some reason.
