📢 New Improvements for Jira and Confluence Automation

[#1]

👋 Hi Community! Sophia from Automation platform here with 4 new improvements:

1. Improved Scheduled Trigger: It is now easier than ever to schedule your triggers, with new start date, end date, and occurrence options.

2. Filter rules by ‘Audit Log ID’: In the Audit Log, you can now quickly find the rule that you want by filtering for the ID.

3. ‘Compatible actions’ in Jira: For some components, you’ll see that by default, only compatible actions are shown to help you create rules that will accurately run as you intend them to.

4. Rule validation in Jira: On rule save, you’ll also be shown warnings when there are incompatible components in your configuration.

Improved Scheduled Trigger

Up until now, the basic options for the Scheduled trigger were limited and lacked flexibility, and we’ve taken into account your feedback regarding the complexity of using advanced CRON expressions.

From now, you will have the capability to easily configure more complex Scheduled triggers. This includes the option to select a start date and an end date, plus specify the number of occurrences. For example, you can set your rule to run on the 4th Wednesday of each month.

This will allow you to schedule rules to run exactly when you intend them to.

Filter rules by ‘Audit log ID’

Until now, the Audit Log has offered limited search capabilities and lacked filters, making it difficult for users to locate specific rules. We’ve listened to your feedback and are working on improving observability in the Audit Log.

We are excited to introduce the first new filter functionality - Audit Log ID. This will enable users to easily filter rules by the Audit Log ID and ultimately save you time. Keep an eye out for new filter and search functionality coming soon!

‘Compatible actions' in Jira

A few months ago, we released a new capability directly into the rule builder in Confluence that essentially acts like guardrails to help you configure rules correctly. I’m thrilled to announce this is now available in Jira!

Next time you start to add a component, in certain cases, you will notice that by default, only ‘Compatible actions’ are displayed. This will help you create rules that will accurately run as you intend them to. However, you can still search for and choose from all other available filters as needed.

Rule validation in Jira

In continuing to improve guidance on rule configuration, when saving a new rule or updating an existing rule, users will now see ‘incompatible warning' messages if there are invalid components. By proactively identifying components that may cause rule execution failures or errors, this will help ensure your rules are configured accurately and reduce the need to look through the audit log to troubleshoot why a rule didn’t work as intended.

This feature is already available in Confluence so we are excited to introduce it to Jira too!

When will it all be available?

These are already available to all Jira and Confluence Premium and Enterprise customers!

We want to hear from you!

As always, we would love to hear your feedback. Please feel free to schedule a chat with us or leave a comment on below.

[Bill Sheboy]

Hi @Sophia Do 

Thank you and the team for these great updates!

Regarding the rule validation item, how would you expect that feature to work when:

• there are multiple errors
• errors within condition blocks
• errors within branching blocks
• errors after either conditions or branching blocks

I did some quick tests and found components inconsistently marked with the "incompatible component" indicator.  Dragging and dropping seemed to cause the same symptoms.  Publishing, exiting to the rule list, and returned for updates / publish did not always re-raise the indicator.  It appeared only the first time and instance of incompatible component was found consistently.

Kind regards,
Bill

[Martin E]

I see many links to blog.codebarrel.io but theyre not valid anymore. Is it still possible to access that information anywhere?

e.g.  https://community.atlassian.com/t5/Automation-articles/Jira-Automation-all-the-resources-you-need-in-one-page/ba-p/1388465 contains links to codebarrel

[florian_reichl_lovebyte_codes]

Would love to see api for custom triggers and custom actions - did I miss something?

[Bill Sheboy]

Hi @florian_reichl_lovebyte_codes -- Welcome to the Atlassian Community!

No, you did not miss anything: there are no custom triggers or actions, and still no REST API for automation rule management.

The closest things to custom triggers and actions might be:

• using the incoming webhook trigger to catch Jira Site, outgoing webhooks for things for which rules have no trigger
• creating external services to perform needed actions and calling those with Send Web Request

And, if a REST API to create / edit rules is added, all bets are off as people will likely start creating dynamic and self-modifying rules!

Kind regards,
Bill