The job Trigger, condition, action Smart values and catches
Share new bugs out across the team Work item created, condition type equals Bug, then Assign with the balanced workload or round-robin option over a list of people. Balanced workload counts open items per person, so someone back from leave gets the next few in a row.
Set a due date from priority Work item created, condition priority equals Highest, then Edit work item to set the due date. {{now.plusBusinessDays(2)}} skips weekends. Add one rule per priority, or an if/else block in a single rule.
Say who reopened something Work item transitioned from Done to In Progress, then Comment on it. {{initiator.displayName}} is the person who moved it. {{issue.assignee.displayName}} is who owns it now.
Start the parent when work starts Work item transitioned to In Progress, condition type is Sub-task, branch to the parent, condition parent status is To Do, then transition it. Without the status check, every later sub-task tries the same move and the audit log fills with errors.
A Monday digest of stale work Scheduled weekly, then Lookup work items with JQL such as updated <= -14d AND statusCategory != Done, then Send email to the lead. {{lookupIssues}} lists them, but only the first 100. Keep the JQL tight.
Ping chat on a Highest-priority bug Work item created or priority changed, condition priority equals Highest, then Send Slack message or Send Microsoft Teams message. {{issue.url}} gives a clickable link. {{issue.key}} alone isn't clickable in chat.
Let another system start a rule Incoming webhook trigger, then whatever actions the event calls for, such as create or transition a work item. Anything the caller sends arrives as {{webhookData}}. Keep the generated URL private: anyone holding it can start the rule.