đź“Ł Introducing Branch with Conditions for Atlassian Automation
Modern teams don’t work in straight lines. An incident can be Sev-1 for one customer and low priority for another. A feature might be ready for engineering but blocked on design. Yet most automations still behave like assembly lines: every item goes through the same steps, in the same order, no matter what’s actually happening.
Today, we’re introducing Branch with Conditions for Atlassian Automation – a new way to build dynamic, decision-aware workflows that automatically take different paths based on real‑time context like priority, customer, status, or request type. Instead of wiring up multiple rules or nesting brittle if/else blocks, you can design a single, smarter workflow that consistently makes the right decision for you.
In this post, we’ll walk through what Branch with Conditions is, when to use it, and how teams are already combining it with advanced components (and Rovo agents) to orchestrate complex workflows across incidents, product development, and more.
What is Branch with conditions?
Branch with conditions lets you automate consistent decision making in your workflows. Instead of every workflow doing the same set of actions every time, Branch with conditions lets your workflow look at what’s happening in real-time, evaluate it and then take the right path automatically: no human decision, or manual routing required.
What problem does it solve?
When automating workflows - especially those managing a business process - you’ll often need to handle different scenarios based on the specific details of a work item or alert. Until now, customers have had limited decision-making control in their workflows, leading to a lack of flexibility when using nested if/else steps or requiring multiple workflows to be created to handle different scenarios. With Branch with condition, automation customers can orchestrate their workflows to react differently based on real‑world context like priority/customer type/request reason/status, ensuring maximum precession, efficiency and control.
How it works
When building or editing an automation workflow, simply add the Branch with conditions component, which can be found under the 'PLUS: Add an advanced component’ section. You can then choose:
-
To branch off a Work item or Alert. NB: Support for Pages and other objects will be coming later.
-
The number of branches: At minimum you need to configure 2 branches, maximum of 3 (not including the Fallback-details below). It’s a good idea to get into the habit of naming your branches to improve readability.
-
The condition value/s for the branch: You can add one or more condition values for each branch using AND logic.
-
Add actions inside each branch: You can use actions, conditions and other workflow control components like Delay until, Branch at the same time, and For each. These will be contained within Groups
-
Fallback branch: If none of the branches match the conditions you’ve set, the default Fallback branch ensures your workflow still proceeds. It is optional if you want to configure actions within the Fallback branch.
How you can use Branch with conditions today
IT Ops Incident management
Once an alert is triaged, create branches for High, Medium and Low priority to route the incident to the appropriate remediation steps and reduce your time to incident resolution.
Advanced: Product development readiness process with multiple Rovo agents
Combine Branch with conditions with your custom Rovo agents + Rovo Dev agent and other orchestration controls - Delay until, Branch at the same time - to remove costly manual checks and tasks to see if a work item is ready for development all whilst keeping your teammates in control.
Workflow breakdown
Let's break down what's happening in a little more detail...
| Highlight | What's happening |
 |
Trigger and conditions:
When Status transitioned to “Ready for Dev evaluation” for a work item. Conditions ensure that only work items with designs and requirements are worked on. |
 |
Readiness Checker Agent: |
 |
Delay Until as a human decision gate: When the agent’s findings are then added as a comment along with clear instructions of next steps. The work item then gets assigned to a reviewer. Then by using Delay until the workflow pauses, waiting for a reviewer to analyse the agent’s analysis before labelling the item as ready or not ready. |
 |
Branch with conditions routes to the right scenario:
|
Try it now - we'd love your feedback
Branch with conditions has started rolling out and will be available to Premium and Enterprise Edition customers by early February 2026. We can’t wait to see how you use it to make your workflows do more for your team. If you have any thoughts, questions, or want to share your use cases, leave a comment below.
Tips and best practices
-
Name branches precisely: Use outcome-oriented names like “Is Ready” and “Needs Work.” These show up in the Audit log to speed up troubleshooting.
-
Keep branch conditions exclusive: Prefer a single owned field (like a label) for branching. Complex logic is harder to maintain and debug.
-
Pair Delay Until with status or label change instructions to create human decision gates: This prevents premature automation and improves quality at handoff points between tasks and work done by Rovo Agents.
FAQ
Q: How many branches can I configure?
A: You can configure up to three branches, plus a Fallback branch for unmatched cases for a total maximum of 4 branches.
Q: Can I combine Branch with Conditions with other advanced components?
A: Yes. Inside each conditional branch you can add actions, conditions, and other workflow controls like Delay until, Branch at the same time, and For each.
Q: What happens if no branch conditions match?
A: When no conditions match, the Fallback branch runs. Optional: add actions and use it as a guardrail to notify your team or set fallback actions.
Q: Where do I find it in the workflow builder?
A: Open your rule, select “PLUS: Add an advanced component,” and choose “Branch with Conditions.” Configure branch names and conditions from the component panel.
Was this helpful?
Thanks!
Simon Chan
9 comments