Problem

Currently any change in the Jira custom field configuration is not detected by automation rules using that field.

For example:

• There is a Select List custom field that contains 3 values: Test1, Test2, Test3
• The field is part of a Jira issue and an Issue Fields condition of an automation rule
• In the rule, the condition is comparing the custom field value with Test1
• The rule succeeds if the issue contains Test1 in that field
• Now change or delete Test1 from the field configuration. Let's say you change it to T4
• At this point, reload the Jira issue which will remove the Test1 from the custom field but the automation condition continues to retain it.

The Issue Fields condition in the automation rule doesn't refresh its Value section even when it contains a deleted/unavailable value. This causes the condition to check for an incorrect value leading to rule failure.

Suggested Solution

Automation conditions should detect the absence of a custom field value automatically if the value has been changed/deleted in the field configuration.

Why This Is Important

The condition will not succeed leading to the impact on the automation rule result.

• If there is a change in the values of a field, an automation rule dependent on that field will continue to fail because the Issue Fields condition doesn't know about the change.
• If a field value used in automation is deleted, the rule condition continues with an incorrect comparison resulting in failure. This can cause considerable business impact.
• Users will need to make changes to the automation rules manually which is a lot of manual work. If such changes in field configuration and the number of rules depending on the field are huge, a lot of time is spent on manual correction in multiple places.

Workaround

Keep track of the changes in the field values and then update the rules manually.