Migrating with JCMA will update Sprint Start Date with the Activation Date

On Data Center, Sprints contain data stored inside the table AO_60DB71_SPRINT. Two important columns in this table are:

• START_DATE: The Sprint's planned Start Date
• ACTIVATED_DATE: The Sprint's actual Start Date (when the "Start Sprint" action was performed)

Reference: How to update the dates of a closed Sprint in Jira

In Jira Cloud, Sprints only have the START_DATE column which represents the actual start date of the sprint. As a result, when migrating from DC to Cloud, the ACTIVATED_DATE will be the value that populates the START_DATE value in Cloud.

This behavior can be misleading to customers who expect the START_DATE to match but that won't always be the case.

Suggestion

It would be helpful if this behavior was explained to customers who are migrating sprints. Logging this value would make it easier to understand how the start date is getting populated.

Another option would be to have both START_DATE and ACTIVATED_DATE available in Cloud so that the mapping matches completely.