Issue Summary

Object-ticket connection reindexing running on a single thread, ignoring Assets parallelism.

On instances having many Assets objects associated with many Jira issue (e.g. object-ticket connections), usage of single thread becomes more obvious, since Assets reindexing is taking a lot of time (several hours or more).

Steps to Reproduce

1. Configure Assets parallelism to user more 1 thread
2. Start clean reindex

Expected Results

Assets reindexing is using optimal number of threads to reindex object-ticket connections.

Actual Results

Reindexing object-ticket connections is being done by a single thread, ignoring parallelism.

Workaround

There is no workaround at this point. Workaround will be added when available.