We have identified significant performance issues with Assets imports and object history lookups in Jira Service Management Data Center (JSM DC) 5.7+ due to the lack of database indexing and the introduction of a new history check during imports. One our Customer's investigation and workaround may be valuable for Development team to consider for future improvements.

Background:

• After upgrading to JSM DC 5.7, we observed that Asset import jobs became extremely slow (e.g., a job that previously took 2 hours ballooned to 14 hours).
• Investigation revealed that the new import logic introduced in 5.7 performs a history lookup for all objects, which was causing the slowdown.
• As a workaround, the Customer enabled the dark feature flag insight.import.update.missing.object.only.if.ever.imported.disabled (per this bug) which bypasses the history check. This restored import performance to normal levels.

Additional Findings:

• Even after the import performance was restored, accessing the “History” tab for any Asset object in the GUI remained extremely slow (sometimes taking minutes to load).
• Their DBA manually added a database index to the AO_8542F1_IFJ_OBJ_HIST table (on the ID field), which immediately resolved the GUI performance issue for history lookups.
• We could not find any documentation indicating that this index should exist by default, nor any mention of it being lost during upgrades.

Suggestions:

• Review and consider adding appropriate database indexes (on the AO_8542F1_IFJ_OBJ_HIST table) by default in future releases to improve performance for large instances.
• Review the import logic introduced in JSM 5.7 to ensure it is performant at scale, or provide configuration options for customers to tune history checks.

Evidence:

• Import jobs slowed from minutes/hours to many hours after upgrade.
• Bypassing history checks via dark feature restored import speed.
• Adding a database index to the history table restored GUI performance for history lookups.
• No official documentation found regarding default indexes or performance tuning for this table.