📣 Unlock Advanced Workflow Orchestration With These New Enhancements

[#1]

We’re excited to announce the rollout the first of a powerful set of new advanced automation features for Atlassian Cloud Premium and Enterprise customers. These enhancements are designed to help you orchestrate end-to-end workflows across teams and products, moving beyond single-task automation to true business process automation.

Why this matters:

• Eliminate manual workarounds: No more chaining rules with hacks—now you can design, visualize, and manage multi-step, multi-team processes natively.

• Boost efficiency: Automate parallel processes, reduce errors, and free your teams to focus on higher-value work.

• Enterprise-grade: Gain visibility, manage complexity, and scale automation across your organization.

Let’s look at some of these new capabilities:

Branch at same time

Run up to three branches of a workflow simultaneously. This is ideal for processes where multiple tasks need to happen at once but don’t depend on each other (e.g., onboarding steps for new employees). All branches auto-join before the workflow continues, ensuring synchronization of task completion.

Groups

Break complex workflows into manageable segments. Each Group can have its own logic, conditions, input, and output values. Groups are automatically created when you add an Advanced component, making it easier to build and maintain sophisticated automation.

Conditions on Trigger

Add conditions directly to your rule triggers. This lets you filter which events start your automation, reducing noise and making your workflows more precise. You can add multiple conditions (with AND logic) to refine even further.

Component Picker

A new component picker section makes it easy to add actions, conditions, branches, and now, Advanced workflow controls (like Run all at once) to your automations. The picker adapts based on where you are in the workflow, ensuring you always see the right options.

Rules List

Quickly find and manage all your automation rules—including those with advanced components. Rules with advanced BPA features are clearly labeled, making it easy to distinguish and manage complex workflows.

Service and Usage Limits

To ensure reliability and performance, new service limits apply to advanced workflows:

• Up to 65 components per group

• Up to 500 components per rule with an Advanced workflow control

• Up to 3 parallel branches per Run all at once

• Up to 32 conditions on trigger

• 1 level of nested branches per branch with Branch at the same time

• Total rule duration up to 15 days with an Advanced workflow control

• For a limited time, customers have access to advanced workflow controls within the Atlassian Acceptable Use Policy. In the future, usage beyond existing Edition Usage Limits will incur additional charges based on consumption. At that time, organization admins will have tools to monitor and manage consumption and will be able to purchase additional capacity.

FAQ

Q: Who gets access to these new advanced capabilities?
A: Branch at the same time, Groups and Condition Filtering on Trigger are available to Cloud Premium and Enterprise customers.

Q: When will I be able to see these new capabilities?
A: We are gradually rolling these out and expect to have them Generally Available by the end of July 2025, and will update this post if this changes.

Q: Can I use these features across Jira, Jira Service Management, and Confluence?
A: Yes! All advanced capabilities are rolling out across all Atlassian Cloud products for eligible editions.

Q: How do I add a Branch at the same time or Group?
A: When you add Branch at the same time, Groups are created automatically for every branch added.

Q: What happens if I delete a branch in Branch at the same time?
A: If you have two or more branches, deleting one will remove the group, but you must have at least two branches configured for the automation to be saved and run.

Q: How do I add a Condition Filtering on Trigger?
These can be added to any automation in eligible editions, with or without an advanced component like Branch at the same time.

Q: Are there limits to how complex my workflows can be?
A: Yes, to ensure performance, the number of components, branches, and workflow duration is limited. See the Service Limits section above.

Q: Where can I learn more or see demos?
A: Stay tuned for more announcements at Team’25 Europe!

We’re committed to helping you automate and orchestrate your most critical business processes. If you have questions, feedback, or need support:

• Visit our Community and ask a question or drop a question on this post

• Contact Atlassian Support via your admin portal

Thank you for being part of our journey to make automation more powerful for your team!

[Rune Rasmussen]

We are very much looking forward to this hitting our site.
There are several automations we've had to chain together in interesting ways that will be much simplified with these features.

Bonus question:

Will the component counter still only be shown (hidden away) in the "add new component" box, or has it been moved out into the "main UI" where it will be visible all the time?

[Sami Shaik]

This is a fantastic update to Automation for Jira! 

The introduction of advanced workflow orchestration features is definitely a game-changer for teams managing complex processes across multiple projects. The ability to:

• Chain multiple rules together
• Pass smart values between rules
• Use more flexible branching options

will help streamline many real-world automation use cases that were difficult to achieve previously.

One small suggestion for improvement: It would be great if the documentation could include more real-world examples for common business processes, and ITSM environments where multi-step automations are critical.

Overall, great work by the Atlassian team — this significantly boosts the power and flexibility of Jira Automation! 

Looking forward to seeing even more enhancements in this area.

[Tobias Bosshard]

We are very pleased about this news. Thanks a lot for your effort!

What I didn't see: whats happen with strikly serial processing of branches? Is this now in logical order or still random?

[Bill Sheboy]

Hi @Simon Chan 

Thank you for the information about the new Enterprise and Premium license features.  It appears the conditions on trigger feature is available for all license levels.

For the feature to add conditions on triggers, will the racetrack timing problems be addressed? 

Specifically, there is a problem where the issue-created (and other events) can start a rule before all work item data is available or even in a stable state.  This creates problems in rule conditions / behaviors, with the workaround of always adding the Re-fetch Work Item Data action immediately after this (and other) triggers. 

There are already open defects for this new feature apparently demonstrating this symptom, with the suggested workaround to not use the feature!

Kind regards,
Bill

[Matthew Challenger]

Woah! Love this. Can't wait for these to roll out to our instances. We've definitely had to rework several automations in the past from hitting that 65 component limit.

[Jerel Crosland]

The obvious question is, will this feature be rolled out to the Data Center edition? If so, roughly when?

[Mikael Sandberg]

I would warn against using parallel branches in an existing automation. We have had this feature for about a week and tried to use in an existing rule that triggers on work item created and the rule went rouge and generated close to 4000 work items because it ignored a condition. There is a bug created for this, see AUTO-1926. Based on my testing this does not happen if you create a rule from scratch.

[Bill Sheboy]

Another observation: the "branch at the same time" feature is only available for Premium and Enterprise levels, but the new rules list filter for "Advanced Components" shows up for all levels, including Free.

Either this is another defect, or...are there other advanced component features to-be-released that will work for all license levels?

[Brandon Davies]

These are a great start! our main pain points are the 100 objects limit on branches and only being able to branch one level deep in an automation, usually we have to use workarounds to fix these, happy to see what comes next! :D 

[Dave Meredith]

I agree with @Tobias Bosshard .

Processing 10 things concurrently in a branch is what was happening anyway. Now you're just processing 3 different sets of actions on 10 things concurrently?

So it's 

[BRANCH 1], [BRANCH 2], [BRANCH 3]

Instead of:

[BRANCH 1]

[BRANCH 2]

[BRANCH 3]

https://jira.atlassian.com/browse/AUTO-32 <<< As described here. I would find it more useful to have serial processing that ensures that in a branch the first items actions have been processed before it moves onto the next item. You need the first thing to happen before the next thing can take place, you need to generate X in step 1 before you can calculate X + Y in step 2.

It's probably more efficient from a shared resource at scale perspective, splitting the actions for execution to run concurrently saves run time and frees up resources for the next org to do stuff. But for me, processing everything at the same time usually causes me more issues than it solves.

[Brita Moorus]

Oh wow, this is really exciting! ✨

[Dirk Ronsmans]

Loving the improvements! I only have questions with these 2 items:

•  Total rule duration up to 15 days with an Advanced workflow control

Really days? I guess that's then combined execution time across branches cause that seems a lot (even then)

• For a limited time, customers have access to advanced workflow controls within the Atlassian acceptable use policy. In the future, usage beyond existing Edition Usage Limits will incur additional charges based on consumption. At that time, organization admins will have tools to monitor and manage consumption and will be able to purchase additional capacity.

Can you elaborate a bit on this? Currently we already have Usage limits on the rule executions, will there be additional usage counters on the advanced components or are we talking more general that the ability to purchase more usage in general will become available? Would love to see some clarification on this one.

Heck i would even like it more if some things were part of an Automation Premium subscription rather than once again try and figure out usage limits and being unable to accurately quote/predict the bill.

 Side-note, if you're ever looking for ideas to add to Automation:

• The ability to disable a certain component/action (without having to remove it while troubleshooting/testing/building)
• The ability to add annotations/comments to rule components

[Hans Polder _Devoteam_]

@Simon Chan ,

Thanks for this update! I am noticing an apparent bug in the 'add conditions to the trigger' functionality. Whenever I create a new rule from scratch and directly add a condition to it like 'Issue type equals Task' - a lot of the Actions (like 'edit issue' and 'add comment' are not available.

Only when I remove the condition from the trigger, most of the actions become available again. Once I've added at least one action (like Add comment), and THEN add conditions to the trigger, it seems that other actions can be added as normal again.