-
Bug
-
Resolution: Timed out
-
Low
-
1
-
Minor
-
Issue Summary
While performing the data copy into the sandbox, an issue causes the copy function from a production site not to work.
Problem 1
An issue with the file attachment date exceeding the recommended DateTime format of ‘YYYY’ instead it gives ‘YYYYY’ which is wrong. This results from migration, which can occur on any DateTime field within Jira.
message: Failed to set attribute 'FileAttachment.created' with value '52801-01-05 16:28:12.0'. Error: Timestamp format must be yyyy-mm-dd hh:mm:ss[.fffffffff]
Problem 2
After a server-to-cloud migration, there might be instances of transferred invalid Unicode characters on Jira issue fields. This will prevent issues from being copied into another database of Jira.
cloud.atlassian.logmon.laas.api.PrivacySafeException: Privacy-safe boxing of a org.xml.sax.SAXException at com.atlassian.jira.bc.dataimport.DefaultOfbizImportHandler.startElement(DefaultOfbizImportHandler.java:336) at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) at org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at com.atlassian.security.xml.RestrictedXMLReader.parse(RestrictedXMLReader.java:95)
Steps to Reproduce
- Perform a copy from production to sandbox for Premium and above subscription
- Copy fails
Expected Results
This error shouldn't restrict the data copy functionality into the sandbox environment as Jira should enhance the cleanup to work against the DB
Actual Results
Error importing data as it fails
cloud.atlassian.provisioning.exception.PermanentProvisioningFailureException: Import task failed: [Error importing data: PrivacySafeException] at com.atlassian.jira.internal.rest.CloudBackupManager.startImport(CloudBackupManager.java:132) at com.atlassian.jira.internal.rest.ImportResource.lambda$importArchive$1(ImportResource.java:105) at com.atlassian.jira.internal.rest.AbstractCloudProvisionerResource.lambda$null$0(AbstractCloudProvisionerResource.java:149) at com.atlassian.workcontext.metrics.Timer.timeWithException(Timer.java:215)
cloud.atlassian.logmon.laas.api.PrivacySafeException: Privacy-safe boxing of a java.lang.IllegalArgumentException at java.sql/java.sql.Timestamp.valueOf(Timestamp.java:224) at org.ofbiz.core.entity.GenericEntity.setString(GenericEntity.java:414) at com.atlassian.jira.bc.dataimport.DefaultOfbizImportHandler.parseValue(DefaultOfbizImportHandler.java:559) at com.atlassian.jira.bc.dataimport.DefaultOfbizImportHandler.startElement(DefaultOfbizImportHandler.java:378) at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) at org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown Source)
Workaround
No workaround available at the moment, please contact support to help
- mentioned in
-
Page Loading...