Create automation rule

Create an automation rule that moves any card with the label Urgent to the Top Priority list when a due date is added and then assign Priya from Ops. Add a comment on the card stating Deadline assigned and notify the #ops Slack channel. Rule must only run on this board and only for cards created after today.

Before I build the rule that moves Urgent cards, make it easy for reviewers to approve: show the failure modes (e.g., repeated moves if someone edits due date), expose how it interacts with the existing Weekly Triage rule, surface the exact assignment logic for Priya when she is already assigned, and highlight the notification text that will post to #ops.

I just created a rule to move cards labeled Urgent when a due date is set, but during testing the rule moved a card without the Urgent label. Maya reviewed the demo and will want an explanation. I’m not sure whether the trigger condition is mis-specified or if an earlier rule is relabeling cards before this fires. What is the most likely diagnosis and the safest immediate fix so I can present it to Maya?

Over the last quarter we’ve built many small automation rules and now they trigger each other unpredictably, costing the team time reconciling card state. Where do we apply guardrails so new rules don’t cascade: a rule registry with owner and purpose, a test board and a runbook for conflict checks, or a merger process that reviews new rules against existing ones? Recommend one practice to start this week and how to measure improvement.