📣 New automation enhancements to Unlock Advanced Workflow Orchestration

[#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.

Let’s look at some of these new capabilities:

Branch at same time: Run up to three branches of a workflow simultaneously. Read more on branch at the same time here.

Groups: Break complex workflows into manageable segments. Read more on configuring rule groups here.

Conditions on Trigger: Add conditions directly to your rule triggers improving usability of conditions that apply to the incoming event - letting you filter which events start your automation (similar to existing conditions). Read more here.

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. 

Rules List: Quickly find and manage all your automation rules—including those with advanced components. 

Interested in learning more?

Check our post on Automation community for more details.

All your feedbacks and questions are important to us and, are key drivers of our roadmap. 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

And if you have any questions or feedback for us, please book some time based on your availability using this link: https://calendly.com/makarandgomashe/new-meeting

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

[Marcell Bendik]

Branch at same time:

It creates names for the branches. It creates groups & add names to the groups. So I can have a better understanding of a complex algorithm.

Would it be natural to think that these names are used in the Audit log to help understand the undeterministic execution and help me improve the automation?

This was one of the first think to try (as no documentation provided) and I do not see the use of the names / tags used in the Audit logs :(

I would find it meaningful / useful to add branch / group names to the Audit log to get a better understanding what happened.

[Brita Moorus]

These are great! ✨

[Bill Sheboy]

Greetings, Community Managers!

This is a duplicate post of the same article posted yesterday here:

https://community.atlassian.com/forums/Automation-articles/Unlock-Advanced-Workflow-Orchestration-With-These-New/ba-p/3057396

Please remove this article as it will dilute the focus and feedback from community members. 

Thank you, and kind regards,
Bill

[__ Jimi Wikman]

These are awesome additions!

Great work as always team!!

[Kai Becker]

This is awesome. Especially the parallel branching is something that will really help. Thanks!