Problem
When issues are imported into Jira Service Management via CSV, the imported issues have no issue history beyond a single "Issue Created" event. Jira Service Management calculates SLAs dynamically from issue history events (status transitions, first response events, etc.). As a result:

• Imported issues display SLAs as permanently breached or uncalculated
• JSM dashboard gadgets and marketplace SLA reporting apps show incorrect data
• The original SLA compliance history from the source system is unrecoverable after import
This affects any customer migrating from a non-Jira system to JSM via CSV — a very common scenario.
Current Workarounds (Insufficient)

• Remove SLA target for imported issues entirely — loses all SLA reporting
• Bulk transition to create history — timestamps reflect time of transition, not original timeline
Proposed Solution
Add optional CSV column mappings (e.g. Created Date, First Response Date, Resolved Date, Status Change Date) that allow the CSV importer to construct synthetic issue history events, enabling the SLA engine to calculate values correctly.
At minimum, mapping Created Date + Resolved Date would allow basic Time to Resolution SLA to be calculated correctly.
Customer Impact
This was reported by an enterprise customer (SEN-30150398) who imported ~5,000 issues from Excel into JSM and found all SLAs permanently broken in their dashboard gadgets and marketplace SLA app. This is a repeatable pattern for any customer migrating via CSV.
Steps to Reproduce

1. Import issues into a JSM project via CSV
2. Open the imported issues — note SLAs show as breached or running indefinitely
3. Check the issue changelog — only a single "Issue Created" event exists, no history
Expected Behavior CSV import should support optional date column mappings that allow the importer to create synthetic history events, enabling SLA calculation based on original ticket dates.
Actual Behavior No issue history is created for CSV-imported issues. SLAs are always incorrect after CSV import.
References

• KB: https://support.atlassian.com/jira/kb/sla-keeps-counting-for-closed-issues-imported-via-csv/