Summary

When updating issues' values using Proforma, and using the Issue Created trigger, automation rules are not working correctly. If the user is comparing fields from Proforma before executing an action they will see the message below on the Automation Rule log:

The following issue did not match the condition

Environment

• Jira Server/Data Center on any version from 8.0.0
• Automation For Jira (A4J) Server/Data Center on any version from 7.4.0

Cause

Proforma is designed to update the issues after they are created. On busy instances, there can be several seconds between the issue being created and Proforma updating them, and the issue being re-indexed on Jira indexing files.

Due to this, when the Automation Rule kicks in the data is not yet available so the comparison results in an empty value, thus not matching the condition.

Diagnosis

1. Change the rule trigger to Manual
2. From within the Jira View Issue screen, trigger the Automation Rule (on the "More" dropdown, select the rule name)
3. If the rule has been executed correctly, then the problem is indeed the delay which we mentioned in the Cause section of this article
4. Change the rule trigger back to the original one

Solution

To work around this issue, we will need to fetch the issue data multiple times, so that the rule can be executed based on the most of up to date field values: 

1. Edit the Automation Rule
2. Add three "Re-fetch issue data" before the Condition, right after the "Issue Created" trigger
   1. For each Re-fetch action, click on the "More" option and change the delay to 5 seconds 
3. Save the rule
4. Trigger the rule again and verify if the problem is resolved