...
After snapshot & deployment, the start sprint dates are not correct.
...
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.
Code Block |
---|
SELECT * FROM "AO_60DB71_SPRINT" WHERE "STARTED" = true and "NAME" like '%abc%' |
Info |
---|
All affected sprints (not only those abc) are ending START_DATE with four 0000. All other sprint do have common values. CLOSED COMPLETE_DATE END_DATE GOAL ID NAME RAPID_VIEW_ID SEQUENCE STARTED START_DATE ACTIVATED_DATE AUTO_START_STOP SYNCED |
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
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 The customer could use the generated JSON file to check the mapping of the sprints after the deployment. Then they could update the activated date of the target sprints in the AO_60DB71_SPRINT db table for the corresponding sprints in the target system to the sprints in the source instance.
Info |
---|