Introduction

When displaying an issue, the value of all its Calculated (Scripted) fields is re-computed on-the-fly. This means that the value of any Calculated field will always be up-to-date.

However, when searching for issues, Jira uses the the Jira index instead, which stores the value of all standard and custom fields and is only updated when an issue is modified (or the index is re-built).

This is generally not a problem if the Groovy script of a Calculated field only refers to other fields of the current issue , because if any of these other fields is modified, the issue will be considered as modified and thus the issue will be re-indexed by Jira. However, if the script accesses data from other, related issues issues, such as sub-tasks, linked issues, stories of an Epic, etc., the issue will will not be  be re-indexed if one of the related issues is modified, which can lead to the index becoming obsolete for that issue, thus making search results incorrect.

To work around this limitation, JMCF can force Jira to re-index index related issues when  when an issue is modified. However, this will increase the Jira workload and it should, therefore, be used with caution, and only on projects and/or issue types where it is needed, and only for the right issue relationships.NEEDS at least one example script, with the corresponding auto-indexing rule.