Issue Summary

Multiple concurrent updates to the same issue in the same second can result in inconsistent full-text search index for the customfields that are updated by one of the activities. See https://jira.atlassian.com/browse/AUTO-238 for a related request.

The impact is that full-text search (CONTAINS operator) will not be able to find the issue by filtering on the customfield.

Steps to Reproduce

This is difficult to reproduce as it relies on a race-condition.

From the past investigation the flow seems to be
1. Add two customfields to the issue type, both plain string type
2. Set up automation 1 to copy the value of customfield 1 to customfield 2 when customfield 1 changes
3. Set up automation 2 to update the issue status when customfield 1 changes from "alice" to "bob"
4. Update customfield 1 to "bob"

Expected Results

When running a JQL query like (pseudocode) ...

project = <project> and customfield_1 ~ "bob"

then the issue is found.

Actual Results

The issue is NOT found.

Workaround

When setting up concurrent automation rule, try to apply some random jitter of a few seconds before reacting to issue changes. E.g. in case of Automation for Jira, use the Delay action: https://community.atlassian.com/t5/Jira-Service-Management-articles/Automation-delay-action-new-3rd-party-connector-updates-are-now/ba-p/2756730#M4836