How to fix a sprint's activated date which is not exported as part of a migration [PS]

Owned by Sudhir Kv
Last updated: Sept 19, 2023 by Bogdan Kosev
2 min read

Fixed in Configuration Manager for Jira (CMJ) 6.10.7


This article explains how to fix a sprint's activated date which is not exported during migration but only the start date is exported.

Problem

After a snapshot deployment, the start sprint dates are not showing correctly.

Cause

The Configuration Manager for Jira (CMJ) app does not 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 incorrect results.

SELECT * FROM "AO_60DB71_SPRINT" WHERE "STARTED" = true and "NAME" like '%abc%'

All affected sprints are ending START_DATE with four 0000s.

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

  1. Generate the mapping of the configuration objects' native IDs from the snapshot to the matched objects' IDs from the current system.

  2. 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 [General Setting|https://appfire.atlassian.net/wiki/spaces/CMJ/pages/82775728/General+Settings]

  3. Use the generated JSON file to check the mapping of the sprints after the deployment.

  4. 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 using the ALTER command on the AO_60DB71_SPRINT table.