Customer is seeing Duplicate values are created in the Time in Status custom field in the logs.
The steps so trigger the Duplication in the Time in Status Field have not yet been fully identified and cannot be reliably reproduced.
The error is logged and the duplicate value is not corrected.
At many cases, when we check the customer customfieldvalue table, we don't see any duplicate, which implies that we might be seeing a race condition scenario.
Action to cause Duplicate Unknown
Once Duplication occurs trigger a workflow transition on the affected issue
When Duplicate is detected it is deleted and correct value applied to time in status.
The custom field value shouldn't be changes by more than 1 thread in the same time.
The follow 3 error exceptions are thrown in the atlassian-jira.log file and the Duplicate value is not removed and time in status is not updated with new value:
eventually we don't find the duplicates in the database, but the JIRA performance is impacted and at cases indexing speed gets very slow.