Context

On the Field Value changed automation component, the options available in Change type option may be confusing for some customers because it works differently from how it should work based on the verbiage.

E.g: Automation rule should trigger if changes happen on Sprint field in an issue, depending on which value is set for Change type option the results may be different depending on the change, considering the below scenarios:

The Value deleted option is selected, and then you create a new issue with the Sprint field empty.

Action 1: A value is added to the Sprint field --> Automation rule will not be triggered
Action 2: A value is changed in the Sprint field --> Automation rule will be triggered
Action 3: Value is removed from the Sprint field (field is empty) --> Automation rule will be triggered

The Value added option is selected, and then you create a new issue with the Sprint field empty.

Action 1: A value is added to the Sprint field --> Automation rule will be triggered
Action 2: A value is changed in the Sprint field --> Automation rule will be triggered
Action 3: Value is removed from the Sprint field (field is empty) --> Automation rule will not be triggered

The Any changes to the field is selected, and then you create a new issue with the Sprint field empty.

Action 1: A value is added to the Sprint field --> Automation rule will be triggered
Action 2: A value is changed in the Sprint field --> Automation rule will be triggered
Action 3: Value is removed from the Sprint field (field is empty) --> Automation rule will be triggered

Suggestion

Some actions that are perceived as a value update (change a current value for a new one) will trigger the issue if value deleted or value added is selected, even though it makes change from a backend perspective, it would be better if:

The Value deleted option is selected, and then you create a new issue with the Sprint field empty.

Only triggers if the value is removed from the Sprint field (field is empty)

The Value added option is selected, and then you create a new issue with the Sprint field empty.

Only triggers if a value is added to the (empty) Sprint field.

The Any changes to the field is selected, and then you create a new issue with the Sprint field empty.

Action 1: A value is added to the Sprint field --> Automation rule will be triggered
Action 2: A value is changed in the Sprint field --> Automation rule will be triggered
Action 3: Value is removed from the Sprint field (field is empty) --> Automation rule will be triggered

With the above in mind, one of the option should be renamed to "Value updated" or it should work exactly as their verbiage.