Why do IDs of all components in an Automation rule change when rule is updated?

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform Notice: Cloud - This article applies to Atlassian products on the cloud platform.

Summary

All the triggers, actions, conditions and branches added in an automation rule are called its components. Each component has its own unique ID that is visible if we export an automation rule. Below is an extract of the automation rule JSON file where we can see the Trigger component's id:

Everytime any change is made to automation rule, it is assumed that ID will change only for the component that is updated. However, once the rule is update, ID of each and every component in that rule is updated.

Environment

Cloud

Explanation

ID of each component changes because everytime the rule is updated, system recreates the entire rule by re-inserting each component instead of just modifying the existing component. This method simplifies the process of updating the automation rule, especially considering the intricacies involved in reordering and branching logic. This method ensures that automation logic is correct the same when some change is introduced.



Last modified on Feb 20, 2024

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.