Issue Summary

When an item has custom fields with information and is cloned using the normal clone feature, automation for Jira can treat that as a field value change.

Normally, when items are created, including the clone action, the initial fields should not be considered as updates.

Steps to Reproduce

1. Create an automation flow with a field value changed trigger that monitors a custom field
2. Clone an item that has data in that custom field

Expected Results

The automation should not be triggered because this is a create action, not an update

Actual Results

The automation rule triggers

Workaround

Currently, there is no known workaround for this behavior. A workaround will be added here when available