Automation Rules for Issue Created trigger are not working when using Proforma fields
プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Fisheye および Crucible は除く
要約
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
原因
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.
ソリューション
To work around this problem, first, let's try to isolate this down to either the trigger or the condition itself.
- Change the trigger to Manual, and then from within the issue, trigger the Automation Rule (on the "More" dropdown, select the rule name)
- If the rule has been executed correctly, then the problem is indeed the delay which we mentioned above;
- In the Automation Rule, add three "Re-fetch issue data" before the Condition, right after the "Issue Created" trigger;
- For each Re-fetch action, click on the "More" option and change the delay to 5 seconds
- Now update the rule and verify if the problem is resolved;