Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Migrate Jira project from cloud to server

Dennis Bursy June 20, 2019

Hi everyone!  

I want to import a single jira project from our cloud version to our server hosted version(7.10.1)

 

Therefore i create a full backup from the cloud and restore it into a temp jira instance. (same version as our version)

Frome there i generated again a full backup.

 

Now i want to import the project, but i got the message that the custom fields does not fit.

 

First i tried the import in another temp jira (same version) then i become the message i posted in this thread (locked custom field option not available)

https://community.atlassian.com/t5/Jira-questions/Custom-fields-problem-migrate-jira-project/qaq-p/1111418#M353968

 

Then i tried it in our version, the problem is now the language.

All is configured to german. 

 

Only the name of the locked custom field seems to be the problem. Even the description from the locked custom field is german.

--------------------------------------------------------------------------------------------------

"Das benutzerdefinierte Feld 'Epic Color' vom Typ 'Farbe des Epic' ist für den Import erforderlich, aber existiert nicht in der aktuellen JIRA-Instanz."

---------------------------------------------------------------------------------------------------

 

The name in our version is not 'Epic Color'. It is 'Epic Farbe'

 

Have you any suggestions?

 

best regards

Dennis

 

 

 

 

 

 

2 answers

1 accepted

1 vote
Answer accepted
Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 21, 2019

Hi Dennis,

I understand you are looking to migrate a project from Jira Cloud to Jira Server and that you have already restored that full cloud back to an intermediary Jira Server instance.  I can see the error you are getting here.  It looks like the name of this system field is slightly different from the Cloud backup than it is compared to the destination Jira site.

You should be able to make an adjustment to this field in the temp Jira site (that has had the full cloud backup restored to it).  There is a method you can use to unlock this system field documented in How to unlock a Locked Jira Software Field.  With the field name unlocked you can rename that field.   I would recommend setting these field names to be exactly the same as they are in the destination Jira site.

Once this is complete, you will likely be prompted to reindex Jira on that temporary site.  Although I'm not sure thats really needed, since really I think you would just need to create a new XML backup from that temporary Jira site, and then use that backup file when using the project import steps on the destination site.

I hope this helps.

Andy

0 votes
Dennis Bursy June 24, 2019

Hi @Andy Heinzer  !

Many thanks,  the solution worked.

 

We were able to import the project. 

 

But now we became this message:

"The import was aborted because there were too many errors"

 

Our houster send us the log-files:

 

Here some section:

2019-06-21 22:33:54,762 ProjectImport: CreateIssues:thread-9 ERROR dennisbursy 1353x1383x1 17l2iae 79.201.166.56,10.3.252.21,0:0:0:0:0:0:0:1 /secure/admin/ProjectImportSummary.jspa [c.a.j.imports.project.DefaultProjectImportPersister] Unable to create issue with key 'ELMS-2700'.
com.atlassian.jira.external.ExternalException: Unable to create issue: ELMS-6904
at com.atlassian.jira.external.ExternalUtils.createIssue(ExternalUtils.java:228)
at com.atlassian.jira.imports.project.DefaultProjectImportPersister.createIssue(DefaultProjectImportPersister.java:145)
at com.atlassian.jira.imports.project.handler.IssuePersisterHandler$1.run(IssuePersisterHandler.java:71)
at com.atlassian.jira.util.concurrent.BoundedExecutor$1.run(BoundedExecutor.java:50)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: com.atlassian.jira.exception.CreateException: com.atlassian.jira.workflow.WorkflowException: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:Issue][summary,Kurskatalog: Wenn ich erst per Text filtere und dann die Tab-Filter nutze, dann greifen die Tab-Filter nicht mehr. ][watches,0][creator,j.z][created,2018-07-13 05:44:34.147][timespent,null][timeoriginalestimate,null][project,10501][description,📎 1 File

_Issue created by the Stride bot in the Bug-Sammlung conversation by J Z._][reporter,j.z][type,10100][priority,3][number,6904][environment,null][security,null][timeestimate,null][duedate,null][resolutiondate,null][votes,0][assignee,kalle.ott][id,22363][updated,2018-10-25 10:05:45.619][workflowId,22363][status,10304] (SQL Exception while executing the following:INSERT INTO jiraissue (ID, pkey, issuenum, PROJECT, REPORTER, ASSIGNEE, CREATOR, issuetype, SUMMARY, DESCRIPTION, ENVIRONMENT, PRIORITY, RESOLUTION, issuestatus, CREATED, UPDATED, DUEDATE, RESOLUTIONDATE, VOTES, WATCHES, TIMEORIGINALESTIMATE, TIMEESTIMATE, TIMESPENT, WORKFLOW_ID, SECURITY, FIXFOR, COMPONENT) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) (Incorrect string value: '\xF0\x9F\x93\x8E 1...' for column 'DESCRIPTION' at row 1))
at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:519)
at com.atlassian.jira.issue.managers.RequestCachingIssueManager.createIssue(RequestCachingIssueManager.java:204)
at com.atlassian.jira.external.ExternalUtils.createIssue(ExternalUtils.java:220)
Caused by: com.atlassian.jira.workflow.WorkflowException: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:Issue][summary,Kurskatalog: Wenn ich erst per Text filtere und dann die Tab-Filter nutze, dann greifen die Tab-Filter nicht mehr. ][watches,0][creator,j.z][created,2018-07-13 05:44:34.147][timespent,null][timeoriginalestimate,null][project,10501][description,📎 1 File

_Issue created by the Stride bot in the Bug-Sammlung conversation by J Z._][reporter,j.z][type,10100][priority,3][number,6904][environment,null][security,null][timeestimate,null][duedate,null][resolutiondate,null][votes,0][assignee,kalle.ott][id,22363][updated,2018-10-25 10:05:45.619][workflowId,22363][status,10304] (SQL Exception while executing the following:INSERT INTO jiraissue (ID, pkey, issuenum, PROJECT, REPORTER, ASSIGNEE, CREATOR, issuetype, SUMMARY, DESCRIPTION, ENVIRONMENT, PRIORITY, RESOLUTION, issuestatus, CREATED, UPDATED, DUEDATE, RESOLUTIONDATE, VOTES, WATCHES, TIMEORIGINALESTIMATE, TIMEESTIMATE, TIMESPENT, WORKFLOW_ID, SECURITY, FIXFOR, COMPONENT) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) (Incorrect string value: '\xF0\x9F\x93\x8E 1...' for column 'DESCRIPTION' at row 1))
at com.atlassian.jira.workflow.OSWorkflowManager.createIssue(OSWorkflowManager.java:768)
at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:510)
... 8 more
_Issue created by the Stride bot in the Bug-Sammlung conversation by J Z._][reporter,j.z][type,10100][priority,3][number,6904][environment,null][security,null][timeestimate,null][duedate,null][resolutiondate,null][votes,0][assignee,kalle.ott][id,22363][updated,2018-10-25 10:05:45.619][workflowId,22363][status,10304] (SQL Exception while executing the following:INSERT INTO jiraissue (ID, pkey, issuenum, PROJECT, REPORTER, ASSIGNEE, CREATOR, issuetype, SUMMARY, DESCRIPTION, ENVIRONMENT, PRIORITY, RESOLUTION, issuestatus, CREATED, UPDATED, DUEDATE, RESOLUTIONDATE, VOTES, WATCHES, TIMEORIGINALESTIMATE, TIMEESTIMATE, TIMESPENT, WORKFLOW_ID, SECURITY, FIXFOR, COMPONENT) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) (Incorrect string value: '\xF0\x9F\x93\x8E 1...' for column 'DESCRIPTION' at row 1))
at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.createValue(DefaultOfBizDelegator.java:299)
at com.atlassian.jira.ofbiz.WrappingOfBizDelegator.createValue(WrappingOfBizDelegator.java:172)
at com.atlassian.jira.entity.EntityUtils.createValue(EntityUtils.java:35)
at com.atlassian.jira.issue.IssueImpl.store(IssueImpl.java:1150)
at com.atlassian.jira.workflow.function.issue.IssueCreateFunction.execute(IssueCreateFunction.java:72)
at com.opensymphony.workflow.AbstractWorkflow.executeFunction(AbstractWorkflow.java:1014)
at com.opensymphony.workflow.AbstractWorkflow.transitionWorkflow(AbstractWorkflow.java:1407)
at com.opensymphony.workflow.AbstractWorkflow.initialize(AbstractWorkflow.java:606)
at com.atlassian.jira.workflow.OSWorkflowManager.createIssue(OSWorkflowManager.java:742)
... 9 more
Caused by: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:Issue][summary,Kurskatalog: Wenn ich erst per Text filtere und dann die Tab-Filter nutze, dann greifen die Tab-Filter nicht mehr. ][watches,0][creator,jesko.zychski][created,2018-07-13 05:44:34.147][timespent,null][timeoriginalestimate,null][project,10501][description,📎 1 File

_Issue created by the Stride bot in the Bug-Sammlung conversation by J Z._][reporter,j.z][type,10100][priority,3][number,6904][environment,null][security,null][timeestimate,null][duedate,null][resolutiondate,null][votes,0][assignee,kalle.ott][id,22363][updated,2018-10-25 10:05:45.619][workflowId,22363][status,10304] (SQL Exception while executing the following:INSERT INTO jiraissue (ID, pkey, issuenum, PROJECT, REPORTER, ASSIGNEE, CREATOR, issuetype, SUMMARY, DESCRIPTION, ENVIRONMENT, PRIORITY, RESOLUTION, issuestatus, CREATED, UPDATED, DUEDATE, RESOLUTIONDATE, VOTES, WATCHES, TIMEORIGINALESTIMATE, TIMEESTIMATE, TIMESPENT, WORKFLOW_ID, SECURITY, FIXFOR, COMPONENT) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) (Incorrect string value: '\xF0\x9F\x93\x8E 1...' for column 'DESCRIPTION' at row 1))
at org.ofbiz.core.entity.GenericDAO.singleInsert(GenericDAO.java:206)
at org.ofbiz.core.entity.GenericDAO.insert(GenericDAO.java:171)
at org.ofbiz.core.entity.GenericHelperDAO.create(GenericHelperDAO.java:89)
at org.ofbiz.core.entity.GenericDelegator.create(GenericDelegator.java:548)
at org.ofbiz.core.entity.GenericValue.create(GenericValue.java:114)
at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.createValue(DefaultOfBizDelegator.java:296)
... 17 more
Caused by: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:INSERT INTO jiraissue (ID, pkey, issuenum, PROJECT, REPORTER, ASSIGNEE, CREATOR, issuetype, SUMMARY, DESCRIPTION, ENVIRONMENT, PRIORITY, RESOLUTION, issuestatus, CREATED, UPDATED, DUEDATE, RESOLUTIONDATE, VOTES, WATCHES, TIMEORIGINALESTIMATE, TIMEESTIMATE, TIMESPENT, WORKFLOW_ID, SECURITY, FIXFOR, COMPONENT) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) (Incorrect string value: '\xF0\x9F\x93\x8E 1...' for column 'DESCRIPTION' at row 1)
at org.ofbiz.core.entity.jdbc.SQLProcessor.executeUpdate(SQLProcessor.java:570)
at org.ofbiz.core.entity.GenericDAO.singleInsert(GenericDAO.java:198)
... 23 more
Caused by: java.sql.SQLException: Incorrect string value: '\xF0\x9F\x93\x8E 1...' for column 'DESCRIPTION' at row 1
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:965)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3912)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2530)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2683)
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2486)
at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1858)
at com.mysql.jdbc.PreparedStatement.executeUpdateInternal(PreparedStatement.java:2079)
at com.mysql.jdbc.PreparedStatement.executeUpdateInternal(PreparedStatement.java:2013)
at com.mysql.jdbc.PreparedStatement.executeLargeUpdate(PreparedStatement.java:5104)
at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1998)
at org.apache.commons.dbcp2.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:98)
at org.apache.commons.dbcp2.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:98)
at org.ofbiz.core.entity.jdbc.SQLProcessor.executeUpdate(SQLProcessor.java:562)
... 24 more

 

Have you any solution here ? 

I found this Link:

https://confluence.atlassian.com/jirakb/project-import-on-jira-server-might-fail-after-migrating-from-jira-cloud-958783501.html

 

Is this the same problem ?

 

Best regards

Dennis

Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 24, 2019

Hi Dennis,

Glad to hear the first problem is solved.  This second problem is a completely different problem with a different cause.  You can see in your stacktrace two different bits of information that give this one away:

[description,📎 1 File
_Issue created by the Stride bot in the ...

and the latter:

(Incorrect string value: '\xF0\x9F\x93\x8E 1...' for column 'DESCRIPTION' at row 1))

We only see this error when your issue data in Jira contains a 4-byte character like that paperclip character 📎 AND you're using a mysql database with Jira on the backend. This happens because MySQL databases could not store these 4-byte characters correctly.  So Jira throws this error to let you know your data could not be stored.  Jira Cloud sites are all using Postgresql databases, so they are never affected by this problem. 

There is a bug ticket about this in JRASERVER-36135.  This was a  That bug ticket has been marked as resolved, but that is because we now have a means to support mysql in a setup that can avoid this problem.  Before MySQL 5.7 there was not an officially supported way to fix this with that database.  It caused many users to either try to edit there backup data to remove these emojis and other 4-byte characters, or abandon mysql altogether.

If you're using MySQL 5.7.x version for your Jira database, then you should be able to avoid this problem by following the steps in Connecting Jira applications to MySQL 5.7.  It will have you use the utf8mb4 encoding/collation that can then store these characters properly.

Cheers,

Andy

Suggest an answer

Log in or Sign up to answer