Migration of Jira Server 6.2 to Latests cloud version

[Sai Krishna]

Hi

Currently are using the Jira 6.4 version which was purchased in 01/Sep/13 and its license is   expired on 01/Sep/14. We want to migrate to latests Jira cloud version , Since our license is expired  , can we renew the existing license and start upgrade from 6.2 version to 7.0, which is mentioned in below  documentation

https://confluence.atlassian.com/adminjiraserver070/upgrading-jira-applications-749382701.html

or should we  buy the new license?

please provide your inputs for our smooth migration to latests cloud server.

Thanks

Saikrishna

[Andy Heinzer]

You will need to upgrade Jira to 7.0 first before you can begin to think about migrating.  In order to do that, you need to have applied a valid (not expired) license first.  You can just use an evaluation license to do this upgrade.   You can generate these at https://my.atlassian.com

These licenses are only valid for 30 days, but that should be more than enough time to get Jira upgrade and then migrated to Jira Cloud.

I recommend that you follow these steps:

1. Generate evaluation licenses for all your Jira products at https://my.atlassian.com (this includes Jira Agile/Software and Jira Service Desk if you're using either of these).
2. Apply those updated license keys to your existing Jira instance
3. Upgrade to Jira 7.0.x first
4. Then upgrade any/all plugins that you use with Jira to work with this version
5. Once this is done, I would actually recommend upgrading to Jira 7.2.x and then repeating the process of updating your plugins with Jira so that their plugin data can be updated
6. You should then be able to upgrade to the latest version of Jira Server (at this time 7.9.2) and again, update the plugins for that version

Once all that is done, you should be ready to migrate to Jira Cloud. 

[Sai Krishna]

Thanks Andrew, Appreciate your reply, I will try to upgrade as per the mentioned steps.

Thanks

Saikrishna

[Sai Krishna]

Hi Andrew

I have upgraded from Jira6.4.2 to Jira7.0 as per the mentioned steps, Everything looks good except the below issue, On the Login page of JIRA dashboard, below message is seen in Pie-charts section

Unfortunately, one or more of your preferences are now unavailable. Please update your preferences, or remove gadget by clicking delete from the title bar above.

I have seen the Jira logs, but no clue over it why it is coming.

[Andy Heinzer]

Changes were made to Jira between the versions in order to change how users are granted access to Jira and who can see issue data in Jira.   There is a bug for this behavior in https://jira.atlassian.com/browse/JRASERVER-45227

Basically I suspect that your account does not currently have access to see the filter that gadget is using.   That would explain this error message.   I would recommend editing the gadget to see the filter name in use there.  Then see if your account can view that filter in the issue navigator.

I would recommend having the owner of that filter make sure that the filter is actually shared with your account, group, role in Jira.  I think that should help avoid that error.

[Sai Krishna]

Thanks Andrew, It was for Anonymous login.

I have another issue, as per the mentioned steps, I have upgraded from 6.2.4 to 7.0.1, then from 7.0.x to 7.2.14 version , till here everything worked fine, Jira worked as expected, I have upgraded from 7.2.14 to 7.2.9, on loading the addons getting the below error in catalina logs

 DatabaseExternalGauges.JiraDbcpInstruments[instruments=[DBCP_MAX, DBCP_ACTIVE, DBCP_IDLE],objectName=com.atlassian.jira:name=BasicDataSource]
2018-05-24 11:51:07,774 JIRA-Bootstrap WARN      [c.a.jira.health.HealthChecks] Supported database
2018-05-24 11:51:07,806 JIRA-Bootstrap WARN      [c.a.jira.health.HealthChecks] Postgres 8.4.13 is not supported. You should migrate to a supported database version.
    Supported versions are: 9.6, 9.5, 9.4, 9.3
2018-05-24 11:51:07,821 JIRA-Bootstrap WARN      [c.a.jira.health.HealthChecks] Your database is using an unsupported collation
2018-05-24 11:51:07,845 JIRA-Bootstrap WARN      [c.a.jira.health.HealthChecks] Your postgres72 database is currently using an unsupported collation: en_US.UTF-8. You should change this to a supported collation:     - POSIX.UTF-8
        - C.UTF-8
        - C
        - POSIX

    Review our documentation for more information on supported collations.
2018-05-24 11:51:07,873 JIRA-Bootstrap ERROR      [c.a.jira.startup.DefaultJiraLauncher] JIRA has failed to start because of the following errors: [(Event: Level = (EventLevel: fatal) , Key = (EventType: system-plugins) , Desc = We haven't been able to start all the required system plugins , Exception = We couldn't start the following plugins:<br/><ul><li>JIRA Projects Plugin (com.atlassian.jira.jira-projects-plugin)</li><li>Atlassian OAuth Consumer Plugin (com.atlassian.oauth.consumer)</li><li>Atlassian Navigation Links Plugin (com.atlassian.plugins.atlassian-nav-links-plugin)</li><li>Atlassian JIRA - Plugins - Project Config Plugin (com.atlassian.jira.jira-project-config-plugin)</li><li>Applinks - Plugin - Core (com.atlassian.applinks.applinks-plugin)</li><li>Atlassian OAuth Service Provider Plugin (com.atlassian.oauth.serviceprovider)</li><li>Embedded Gadgets Plugin (com.atlassian.gadgets.embedded)</li><li>Gadget Directory Plugin (com.atlassian.gadgets.directory)</li><li>Atlassian JIRA - Plugins - Gadgets Plugin (com.atlassian.jira.gadgets)</li><li>Atlassian JIRA - Plugins - Global Issue Navigator (com.atlassian.jira.jira-issue-nav-plugin)</li><li>Atlassian JIRA - Plugins - Quick Edit Plugin (com.atlassian.jira.jira-quick-edit-plugin)</li><li>Atlassian REST - Module Types (com.atlassian.plugins.rest.atlassian-rest-module)</li><li>Atlassian JIRA - Plugins - REST Plugin (com.atlassian.jira.rest)</li><li>Opensocial Plugin (com.atlassian.gadgets.opensocial)</li><li>atlassian-servlet-plugin (com.atlassian.web.atlassian-servlet-plugin)</li><li>Atlassian JIRA - Plugins - Look And Feel Logo Upload Plugin (com.atlassian.jira.lookandfeel)</li><li>Gadget Spec Publisher Plugin (com.atlassian.gadgets.publisher)</li><li>Atlassian JIRA - Plugins - SAL Plugin (com.atlassian.sal.jira)</li><li>Gadget Dashboard Plugin (com.atlassian.gadgets.dashboard)</li></ul>)]
2018-05-24 11:51:07,913 JIRA-Bootstrap INFO      [c.a.jira.startup.LauncherContextListener] Memory Usage:
    ---------------------------------------------------------------------------------
      Heap memory     :  Used:  303 MiB.  Committed:  990 MiB.  Max:  990 MiB
      Non-heap memory :  Used:  151 MiB.  Committed:  163 MiB.  Max: 1264 MiB
    ---------------------------------------------------------------------------------
      TOTAL           :  Used:  455 MiB.  Committed: 1153 MiB.  Max: 2254 MiB
    ---------------------------------------------------------------------------------

Thanks

Saikrishna

[Andy Heinzer]

There are system plugins that cannot startup with Jira based on your logs.  This usually happens because either other plugins are preventing it, and/or after an upgrade Jira has a tendency to revert back to the default memory allocations, which for large Jira environments are inadequate for starting Jira will all plugins.

1. Stop Jira
2. I recommend following the steps in Increasing JIRA application memory - Atlassian Documentation and allocating memory in line with our Jira Sizing Guide - Atlassian Documentation.
3. then I'd recommend you go to [jira-home]/plugins/installed-plugins/ and move all the contents of this folder into a temp folder outside the jira home.
4. With those files moved, go to your Jira database and run this SQL command:   truncate table pluginstate;
   This will remove all flags in the database that might be preventing plugins from starting.
5. Start Jira

This should allow your upgrade to complete.  Once done, you will want to install all the updated versions of plugins you need.   This includes both 3rd party plugins and Atlassian plugins like Jira Software or Jira Service Desk if applicable.

[Sai Krishna]

Hi Andrew

Thanks for the Support as i was able to upgrade Jira-software for 6.2.4 to 7.2.9 version.

In my current jira cloud account there are 3 projects, i want to import one project from jira cloud to jira server , as in Jira server there is option to import specific project as per the below documentation.

https://confluence.atlassian.com/adminjiraserver071/restoring-a-project-from-backup-802592982.html

When i was trying to import the project getting the below exception in the log and also the attached screenshot.

2018-05-28 12:47:49,364 JiraTaskExectionThread-2 ERROR saikrishna 767x949x1 jwxqvq 14.141.6.170 /secure/admin/ProjectImportSelectBackup.jspa [c.a.j.imports.project.DefaultProjectImportService] There was a problem with the SAX parsing of the file '/var/atlassian/application-data/jira/import/jira-export.zip' when performing a project import.
org.xml.sax.SAXException: No 'key' field for Issue 33102.
com.atlassian.jira.exception.ParseException: No 'key' field for Issue 33102.
    at com.atlassian.jira.imports.project.handler.ChainedOfBizSaxHandler.endTopLevelElement(ChainedOfBizSaxHandler.java:225)
    at com.atlassian.jira.imports.project.handler.ChainedOfBizSaxHandler.endElement(ChainedOfBizSaxHandler.java:169)
    at com.atlassian.jira.imports.project.handler.ChainedOfBizSaxHandler.endElement(ChainedOfBizSaxHandler.java:136)
    at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
    at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(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:103)
    at com.atlassian.jira.imports.xml.DefaultBackupXmlParser$XmlParser.parseXml(DefaultBackupXmlParser.java:115)
    at com.atlassian.jira.imports.xml.DefaultBackupXmlParser.parse(DefaultBackupXmlParser.java:64)
    at com.atlassian.jira.imports.xml.DefaultBackupXmlParser.parseXml(DefaultBackupXmlParser.java:52)
    at com.atlassian.jira.imports.xml.DefaultBackupXmlParser.parseOfBizBackupXml(DefaultBackupXmlParser.java:41)
    at com.atlassian.jira.imports.project.DefaultProjectImportManager.getBackupOverview(DefaultProjectImportManager.java:236)
    at com.atlassian.jira.bc.imports.project.DefaultProjectImportService.getBackupOverview(DefaultProjectImportService.java:194)
    at com.atlassian.jira.web.action.admin.importer.project.ProjectImportSelectBackup$BackupOverviewCallable.call(ProjectImportSelectBackup.java:240)
    at com.atlassian.jira.web.action.admin.importer.project.ProjectImportSelectBackup$BackupOverviewCallable.call(ProjectImportSelectBackup.java:231)
    at com.atlassian.jira.task.TaskManagerImpl$TaskCallableDecorator.call(TaskManagerImpl.java:458)
    at com.atlassian.jira.task.TaskManagerImpl$TaskCallableDecorator.call(TaskManagerImpl.java:426)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at com.atlassian.jira.task.ForkedThreadExecutor$ForkedRunnableDecorator.run(ForkedThreadExecutor.java:216)
    at java.lang.Thread.run(Thread.java:745)
Caused by: com.atlassian.jira.exception.ParseException: No 'key' field for Issue 33102.
    at com.atlassian.jira.imports.project.parser.IssueParserImpl.parse(IssueParserImpl.java:65)
    at com.atlassian.jira.imports.project.populator.IssueIdPopulator.populate(IssueIdPopulator.java:21)
    at com.atlassian.jira.imports.project.core.BackupOverviewBuilderImpl.populateInformationFromElement(BackupOverviewBuilderImpl.java:147)
    at com.atlassian.jira.imports.project.handler.BackupOverviewHandler.handleEntity(BackupOverviewHandler.java:24)
    at com.atlassian.jira.imports.project.handler.ChainedOfBizSaxHandler.endTopLevelElement(ChainedOfBizSaxHandler.java:221)

[Andy Heinzer]

You can't use the project import in Jira Server in order to import projects from a Jira Cloud backup.  I can understand the confusion over this point, it's actually a very common misunderstanding I have seen a number of times in support cases.

You first have to restore the entire Jira Cloud backup to a new Jira Server site, using the setup wizard to 'import existing data' during the setup phase of that new Jira site.   I would recommend that you closely follow this guide: Migrating from Jira Cloud to Server applications to be able to complete the migration of that data successfully first.   Only once that restore is complete can you generate a new Jira Server XML backup of your data from that site and use that for the sake of doing project imports.

There is also an expectation that when you migrating from Cloud to Server, that Jira Server be at the latest available version.  As of today, that is 7.10.0.   

When doing project restorations, there is also an expectation, that the source Jira site where the backup is created from will be on the same version as the destination Jira site.  As such, I would recommend that you restore the cloud backup to a fresh Jira 7.10.0 installation, and also upgrade your existing Jira to the same version.   That way when you go to do the project imports your chances of encountering unexpected problems should be much lower.

[Sai Krishna]

Hi Andrew

I have followed the below two  links and done the migration  of issues,comments  and  also attachments  with the existing users in cloud.

https://confluence.atlassian.com/jirakb/how-to-prepare-a-database-export-for-a-csv-import-from-a-jira-server-application-to-a-jira-cloud-application-779160698.html

https://confluence.atlassian.com/jirakb/bulk-import-attachments-to-jira-issues-via-rest-api-729750741.html

but unable to see the filters , is there any way to export filters using  csv?

Thanks

Saikrishna

[Andy Heinzer]

There is no built in way to export the filters in Jira, short of a full XML backup.  Since it appears you're using the project import, this won't actually be expected to include the filters since these can exist outside the the project scope.

This has been asked before though, check out https://community.atlassian.com/t5/Jira-Core-questions/How-can-I-migrate-Dashboards-and-filters-from-one-JIRA-instance/qaq-p/108357

In it, other users have found that 3rd party plugins like the Configuration manager might be able to help with this.

Alternatively, you could go into the Jira Server instance where you restored the complete XML backup, and then on that Jira database run the command of:

select * from searchrequest;

This will show you the full list of all filters in this Jira instance.  There is not good way to export/import these from Server to Cloud since the project import process is being used here, but it might help in regards to recreating this filters/boards manually in Cloud.