This article explains how to fix the sprint's activated date which is not exported while migration but only exports the start date.
Problem
After snapshot & deployment, the start sprint dates are not showing correctly.
Cause
CMJ doesn't export the sprint's activated date, it only exports the start date. The same date is set as start and activated dates during import.
Example
Execute the below query, and it shows wrong results.
SELECT * FROM "AO_60DB71_SPRINT" WHERE "STARTED" = true and "NAME" like '%abc%'
All affected sprints are ending START_DATE with four 0000.
CLOSED COMPLETE_DATE END_DATE GOAL ID NAME RAPID_VIEW_ID SEQUENCE STARTED START_DATE ACTIVATED_DATE AUTO_START_STOP SYNCED
true 1621347556218 1621411320000 null 303 abc sprint 1 111 null true 1620201720000 null false false
true 1622556888736 1622557080000 306 abc sprint 2 111 null true 1621430280000 null false false
Solution
Generate the mapping of the configuration objects' native IDs from the snapshot to the matched objects' IDs from the current system.
This could be done by enabling the "Persist deployed snapshot to current system native ID mappings" setting in CMJ's general settings page before deployment- https://botronsoft.atlassian.net/wiki/spaces/CMJ/pages/33456130/General+Settings
You could use the generated JSON file to check the mapping of the sprints after the deployment.
Then you could update the activated date of the target sprints in the AO_60DB71_SPRINT Database table for the corresponding sprints in the target system to the sprints in the source instance by ALTER AO_60DB71_SPRINT.