Details
-
Bug
-
Resolution: Fixed
-
High
-
None
-
None
-
None
-
17
-
Minor
Description
Issue Summary
Currently, we don't have any way to directly migrate the JSM projects from one cloud site to another cloud. The recommended step is to restore the backup to a data center and then perform the migration using JCMA. After restoring the backup to DC, the project migration fails with the below error during the export phase.
2022-06-10 12:35:21.203890700 ERROR SF project-export We couldn't export Issue SF-18. Reason: com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException: Unrecognized field "breachTime" (class com.atlassian.jira.migration.export.core.customfield.jsd.CompletedSla), not marked as ignorable (9 known properties: "goalTime", "succeeded", "remainingTime", "elapsedTime", "remainingTimeInDaysAndMillis", "goalTimeUnits", "calendarName", "startTime", "stopTime"]) at [Source: (String)"{"timeline":{"events":[{"date":1649068365135,"types":["START"]},{"date":1649069304184,"types":["STOP"]}]},"ongoingSLAData":null,"completeSLAData":[{"succeeded":true,"goalTime":14400000,"elapsedTime":939049,"remainingTime":13460951,"calendarName":"Sample 9-5 Calendar","startTime":1649068365135,"stopTime":1649069304184,"breachTime":1649082765135}],"metricId":16,"definitionChangeDate":null,"definitionChangeMsEpoch":1641978484795,"goalsChangeDate":null,"goalsChangeMsEpoch":null,"goalTimeUpdatedDate""[truncated 70 chars]; line: 1, column: 347] (through reference chain: com.atlassian.jira.migration.export.core.customfield.jsd.SlaValue["completeSLAData"]->java.util.ArrayList[0]->com.atlassian.jira.migration.export.core.customfield.jsd.CompletedSla["breachTime"]).
This is reproducible on Data Center: (yes)
Steps to Reproduce
- Create a JSM project on the cloud site(make sure it uses breachTime SLA)
- Generate a server backup from the cloud environment.
- Install a temporary DC instance with an evaluation license.
- Restore the backup to the DC environment.
- Use the JCMA to migrate the JSM projects.
Expected Results
The JSM project migration should be successful.
Actual Results
The below exception is thrown in the migration log file:
2022-06-10 12:35:21.203890700 ERROR SF project-export We couldn't export Issue SF-18. Reason: com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException: Unrecognized field "breachTime" (class com.atlassian.jira.migration.export.core.customfield.jsd.CompletedSla), not marked as ignorable (9 known properties: "goalTime", "succeeded", "remainingTime", "elapsedTime", "remainingTimeInDaysAndMillis", "goalTimeUnits", "calendarName", "startTime", "stopTime"])
at [Source: (String)"{"timeline":{"events":[{"date":1649068365135,"types":["START"]},{"date":1649069304184,"types":["STOP"]}]},"ongoingSLAData":null,"completeSLAData":[{"succeeded":true,"goalTime":14400000,"elapsedTime":939049,"remainingTime":13460951,"calendarName":"Sample 9-5 Calendar","startTime":1649068365135,"stopTime":1649069304184,"breachTime":1649082765135}],"metricId":16,"definitionChangeDate":null,"definitionChangeMsEpoch":1641978484795,"goalsChangeDate":null,"goalsChangeMsEpoch":null,"goalTimeUpdatedDate""[truncated 70 chars]; line: 1, column: 347] (through reference chain: com.atlassian.jira.migration.export.core.customfield.jsd.SlaValue["completeSLAData"]->java.util.ArrayList[0]->com.atlassian.jira.migration.export.core.customfield.jsd.CompletedSla["breachTime"]).
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available