Looking for guidance on tracking due date changes

[Adam LaCoste]

I would like to track how often a due date is changed. 

1. I have created a numeric custom field (Due Date Change Counter) default 0
2. I have created an Automation Rule, on Date change, counter update:  current value + 1

This works as expected.  

The problem is that when an issue gets cloned, I have to reset the custom field.  This action is treating the reset as an update causing the custom field to start at 1.

Questions

1. Can anyone offer guidance to resolve this?
2. Can anyone propose a better method of tracking due date changes?

[Aswin Raj D]

Dear @Adam LaCoste ,

You can create another automation for issue created event Tigger and check if due date has value, then set the Due Date Change Counter default 0. I believe this works while you clone as well.