I’m building a rule that is based off of 2 conditions, both single select custom field categories. When using one condition, rule is triggered and adds to project, however when I add the second condition with AND, the rule isn’t triggering even though both conditions are being met. Any help would be appreciated. I’ve tested it with both current tasks and new task.
@Phillip_Gahagans - could you post a screenshot of your rule? Is the first condition being met? If so, then the rule will never get to the second branch because it’s executing branch 1 (i.e., a rule only runs once upon triggering).
1 Like
So within the task I have a single select drop down for each condition and I’ve been selecting both options, it isn’t running. If I remove the 2nd condition it seems to work as it should
1 Like
@Phillip_Gahagans - are you changing strategy initiative second? The way it’s set up, it only triggers when you change that field, so if you haven’t already set sub-strategy initiative to aerospace, the condition will not be met.
Easiest fix is probably to add another trigger for sub-strategy initiative is changed.
2 Likes
Hi @Phillip_Gahagans
Welcome back to the forum.
What @Stephen_Li shared is correct. The problem you are facing is that you created the trigger to be only the first custom field (strategy initiative). So, if the initiative does not change, no matter how many other conditions are added, the trigger will not activate the rule.
One way to fix this issue is to look at a different trigger—for example, when a task is moved to section (x), look for custom field initiatives and sub initiatives. This will make your rule work.
Hope this helps.
1 Like
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.