Automation Billing Attribution, Rule Edits, and Short Field Name Search Improvements

[#1]

Automation billing attribution now follows rule scope and plan limits

We’ve improved how Automation applies billing limits for rules, so usage is now attributed to the correct app based on rule scope. This change aligns with our https://support.atlassian.com/cloud-automation/docs/how-is-my-usage-calculated/#What-are-my-usage-limits.

If a product with a higher automation limit is cancelled or downgraded, and rules previously failed or were limited incorrectly, these rules are no longer aborted. Instead, they’re assigned the correct highest limit at that point, ensuring usage is calculated consistently with your plan’s limits.

This update addresses https://jira.atlassian.com/browse/AUTO-992 and https://jira.atlassian.com/browse/AUTO-1295.

Rule edits no longer cancel in‑progress automation runs

Currently, when you edit an automation rule, any in‑progress executions of that rule are aborted. With this change, in‑progress executions will continue running against the version of the rule they started with, even if you edit the rule afterwards. If a rule is disabled or deleted, its in‑progress executions will still be aborted.

Issue field search now supports short field names

We’ve fixed a problem in the Issue field value changed trigger, where searching for a short custom field name (for example, S) returned too many matches and only showed the first 50 results, making it impossible to select the desired field.

You can now reliably search for and select custom fields with short names in this trigger, without needing to import or edit rule JSON as a workaround.

This update addresses https://jira.atlassian.com/browse/AUTO-1035

[Brandon Davies]

Great updates! Loving the focus and huge upgrades to Atlassian Automation recently 🚀

[Sami Shaik]

@Scott Bell 

Thanks for the update.