Automation For Jira - Some automation rules using the "Field value changed" trigger are not triggered
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. 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.
*Except Fisheye and Crucible
Summary
Some automation rules using the "Field value changed" trigger don't get triggered when the field that they are monitoring is updated.
Diagnosis
If you are able to confirm the points listed below in your Jira application, then this KB article might be relevant:
When checking the history tab of a Jira issue where the field was updated, there is no history entry showing that this field was changed
The 3rd party add-on Field Security Plugin for Jira is installed in the Jira application (this can be checked from the page ⚙ > Manage Apps > Manage Apps)
When this 3rd party add-on is disabled, the automation rule gets triggered as expected
Cause
The 3rd party Field Security Plugin for Jira is known to cause various issues in the Jira application, including but not limited to the ones below:
Automation rules using the Field Value Changed trigger might not be triggered when the field that they are monitoring is updated
The issue history tab might be missing some field changes, as explained in the KB article Jira issue history tab is not showing changes for some fields
When disabling this add-on, the following error might be thrown in the issue history tab
1An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug
Solution
Disable the add-on from the page ⚙ > Manage Apps > Manage Apps to allow the automation rules to be triggered when the field is updated.
Note 1
Please note that a potential side effect of disabling this add-on is the fact that the following error might be thrown in the history tab of some Jira issues:
1
An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug
To fix these errors, it will be necessary to follow the steps below:
Go to ⚙ > Manage Apps > Manage Apps
Look for the add-on and uninstall it
Stop the Jira application (or all the nodes in case of a cluster)
Move the folder "jfs" located in the <Jira_home> folder to a different temporary location
Start the Jira application (or all the nodes in case of a cluster)
Note 2
If you need to keep the add-on Field Security plugin up and running in your Jira application, then our recommendation is to raise a ticket with the add-on support team via their customer portal. This add-on falls outside of Atlassian Support scope since it is not owned by Atlassian
Was this helpful?