Issue Summary

When configuring an automation rule's condition to validate/compare values added on a cascading field, the condition eventually don't work even when the values are placed as expected.

The error happens because of a problem in the Jira hydration mechanism that looks up to options from a cache by id, and fallback to loading from Jira when there was a cache miss. That's why this bug is listed under JRACLOUD.

Steps to Reproduce

1. Create a big number of issues (at least 30)
2. Create a cascading custom field and add it to your issues
3. Add a common value to the field in all your issues. E.G: parent option 1 and child option 1
4. Create an automation rule with an schedule trigger. Set the JQL to execute for all the issues, as this would increase the possibility to reproduce the bug
5. Add a condition in your automation rule to check if the values selected for the cascading field are parent option 1 and child option 2
6. Set any actions after that and run the rule

Expected Results

• The rule's condition should never match, as the values selected for the custom field are not correct.

Actual Results

• Eventually, the condition will return as a match and proceed with the actions, even though the issue values doesn't match the condition.

Workaround

None so far.