nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Unable to import older data into newer JIRA server

James Shablow

The company I work for just purchased a new server, and we would like to migrate out JIRA data, to the new server. We purchased a new starter-license and installed the latest version of JIRA, but there is an error when I try to import the old data onto the new instance.

The version of JIRA on the "old server" (a desktop) is 4.0.2. We are in aerospace, so it is important that we keep all of the history, attachments, etc.

Is there a way to migrate this data to a new version? Perhaps I could install an old version, import the data, the export it, and repeat with newer and newer versions until we got to the latest?

I did read some similar questions, but the solutions did not provide any help.

Thank you in advance,
James

Accepted answers

All comments

Edwin Kyalangalilwa

Hi @James Shablow,

That won't work. Basically you have to install the same version as your current, import the data, then upgrade JIRA.

Migrating Jira applications to another server

Bastian Stehmann

Hi @James Shablow,

@Edwin Kyalangalilwa is right, the easiest and safest way will be to install Version 4.0.2 on your new server, then import the data to that server (there should be no problems as it is the same version) and then upgrade to the newest version.

Please have a look at the upgrade guides for the versions, maybe it will be better not to do the upgrade from 4.0.2 to 7.x but do it in more steps. But there will be hints for this in the upgrade guides.

James Shablow

Thank you both for the quick replies.

The older version currently available is 4.1.1, but the version we have is 4.0.1. Do you think we would be able to import the data with that version, or would be need to find an installer for version 4.0.1?

Bastian Stehmann

I can not say for sure but I think, it should work, so you should just give it a try.

If it does not work, maybe the Atlassian Support might help you with a installer for the version you need.

Edwin Kyalangalilwa

https://www.atlassian.com/software/jira/downloads/binary/atlassian-jira-enterprise-4.0.2-standalone.tar.gz

James Shablow_5a7y89

I found this site explaining how to manually upgrade JIRA from an older version, but it is no longer helpful once I get to step 4.3, as there is no dbconfig.xml file. Additionally, there is no jdbc driver jar file, as mentioned in step 6.4.

Bastian Stehmann

Please have a look at this upgrade guide to upgrade to 4.4, there is also a part what to do when you are upgrading from before 4.3.

https://confluence.atlassian.com/jira064/jira-4-4-upgrade-notes-720413299.html

After that, you can follow that document you found yourself.

James Shablow_5a7y89

Thank you Bastian. I have successfully been able to upgrade to 4.4.5. 6.4, and then 7.0 after starting over from scratch, but after upgrading to 6.4, I lost the ability to Complete issues. I can still create and edit them, but cannot complete them. Any thoughts on what could be causing this? I am wondering if I need to edit the workflow or create a new one.

Bastian Stehmann

At first thought, I do not remember a reason, why this should happen.

Can you give me more information on what happens when you try to complete them?

Is there an error, does nothing happen at all, can't you do the transition?

James Shablow_5a7y89

When I try to complete a PR, a loading screen covers the window, and does not go away until I hit 'Esc'. The PR still has not been completed after doing so. The app log does not show any warnings or errors, after shutting down the JIRA, renaming the old log to start fresh, and restarting it. There are a couple errors when looking at the console in Chrome:

(forgive wall of text, I wan't to provide all of the information in case it is helpful)

When clicking on "Complete":

batch.js:8 Uncaught TypeError: Cannot set property 'onsubmit' of undefined
 at eval (eval at <anonymous> (batch.js:3), <anonymous>:2:27)
 at eval (<anonymous>)
 at batch.js:3
 at Function.globalEval (batch.js:3)
 at HTMLScriptElement.bp (batch.js:3)
 at Function.each (batch.js:3)
 at init.domManip (batch.js:5)
 at init.append (batch.js:4)
 at init.aspect [as append] (batch.js:8)
 at init.html (batch.js:5)
(anonymous) @ VM250:2
(anonymous) @ batch.js:3
globalEval @ batch.js:3
bp @ batch.js:3
each @ batch.js:3
domManip @ batch.js:5
append @ batch.js:4
aspect @ batch.js:8
html @ batch.js:5
_setContent @ batch.js:2543
_setContent @ batch.js:2545
(anonymous) @ batch.js:226
ajaxOptions.complete @ batch.js:2543
completeHandler @ batch.js:232
n @ batch.js:3
fireWith @ batch.js:3
w @ batch.js:5
d @ batch.js:5
XMLHttpRequest.send (async)
send @ batch.js:5
ajax @ batch.js:5
JIRA.SmartAjax.makeRequest @ batch.js:232
ajax @ batch.js:2543
_setContent @ batch.js:2543
_setContent @ batch.js:2545
(anonymous) @ batch.js:226
_show @ batch.js:2543
(anonymous) @ batch.js:2543
n @ batch.js:3
fireWith @ batch.js:3
fire @ batch.js:3
(anonymous) @ batch.js:2547
setTimeout (async)
JIRA.Dialogs.waitForSavesToComplete @ batch.js:2547
show @ batch.js:2543
(anonymous) @ batch.js:2693
dispatch @ batch.js:4
i @ batch.js:4

When loading the issue page:

batch.js:7 ***** Analytics log [kickass.criteriaAutoUpdateEnabled][{"enabled":false}]
batch.js:2686 Your are trying to create a ToggleBlock with selector '.toggle-trigger'.One already exists with this trigger so has been ignored.
init @ batch.js:2686
Class @ batch.js:226
initToggleBlocks @ batch.js:2692
(anonymous) @ batch.js:2692
n @ batch.js:3
fireWith @ batch.js:3
ready @ batch.js:3
B @ batch.js:3
batch.js:2686 Your are trying to create a ToggleBlock with selector '.toggle-trigger'.One already exists with this trigger so has been ignored.
init @ batch.js:2686
Class @ batch.js:226
initToggleBlocks @ batch.js:2692
(anonymous) @ batch.js:2692
n @ batch.js:3
fireWith @ batch.js:3
ready @ batch.js:3
B @ batch.js:3
com.atlassian.jira.jira-issue-nav-plugin:common.js:14 Error while evaluating HTML: Cannot set property 'onsubmit' of undefined, in: <div class="field-group" >
 <label for="resolution">Resolution<span class="aui-icon icon-required">Required</span></label>
 <select class="select" id="resolution" name="resolution">
 <option value="5">
 Cannot Reproduce
 </option>
 <option value="6">
 Fixed
 </option>
 <option value="7">
 Won&#39;t Fix
 </option>
 <option value="8">
 Duplicate
 </option>
 <option value="9">
 Incomplete
 </option>
 <option selected="selected" value="10">
 UNRESOLVED
 </option>
 <option value="11">
 As Intended
 </option>
 </select>
 <a class="localHelp" href="/secure/ShowConstantsHelp.jspa?decorator=popup#ResolutionTypes" onclick="var child = window.open('/secure/ShowConstantsHelp.jspa?decorator=popup#ResolutionTypes', 'jiraLocalHelp', 'width=600, height=500, resizable, scrollbars=yes'); child.focus(); return false;"><img alt="" src="/images/icons/ico_help.png" title="Get online help about Resolution" /></a>
 <div class="description"><script type="text/javascript">
document.jiraform.onsubmit=myFunction;

function myFunction()
{

/* Submit buttons */
 var createB=document.getElementById('Create');
 var updateB=document.getElementById('Update');

/* Form fields */
 var resolutionF=document.getElementById('resolution');

/* Button Pressed */
 if (createB!=null)
 {
 resolutionF.value='none';
 }
 if (updateB!=null)
 {
 if (resolutionF.value==10) resolutionF.value='none';
 }

return true;
}

</script></div>
 </div>
(anonymous) @ com.atlassian.jira.jira-issue-nav-plugin:common.js:14
(anonymous) @ com.atlassian.jira.jira-issue-nav-plugin:viewissue.js:381
b.map.b.collect @ batch.js:247
transformFieldHtml @ com.atlassian.jira.jira-issue-nav-plugin:viewissue.js:381
success @ com.atlassian.jira.jira-issue-nav-plugin:viewissue.js:377
n @ batch.js:3
fireWith @ batch.js:3
w @ batch.js:5
d @ batch.js:5
XMLHttpRequest.send (async)
send @ batch.js:5
ajax @ batch.js:5
JIRA.Issues.ViewIssueController._getFieldsData @ com.atlassian.jira.jira-issue-nav-plugin:viewissue.js:377
JIRA.Issues.ViewIssueController.applyToDom @ com.atlassian.jira.jira-issue-nav-plugin:viewissue.js:377
(anonymous) @ com.atlassian.jira.jira-issue-nav-plugin:standalone-issue.js:2
n @ batch.js:3
fireWith @ batch.js:3
ready @ batch.js:3
B @ batch.js:3

Andy Heinzer

Hi James,

It looks like you have a custom script in one of the field configurations that is not working as expected post upgrade.

<div class="description"><script type="text/javascript">
document.jiraform.onsubmit=myFunction;

function myFunction()
{

^ This isn't native Jira code. So it must have been something added into an older version of Jira to provide some other functionality.

From looking at your error message it looks like your script exists in the description of the resolution field. That particular field is usually only filled in when an issue is completed, so it makes sense to me to look there first. I would recommend trying to remove this custom script for the time being. I think it is causing the screen to hang like this.

If you are not familiar with how to do this, please see Specifying field behavior. It explains how you can add descriptions to fields in Jira. In your case, you will need to go to the field configuration scheme that is in use by this project and edit any fields that might have this script in the description

James Shablow_5a7y89

Thank you Andrew! I looked in the Resolution field in the Field Configuration Scheme that we use, and found the extra code in the Description, as you described above. After removing it the issue was gone.

To figure out why we were even using it, I installed a fresh install of 4.0.2, and restored the backup of the system. I then removed the custom code, and completed a new issue to discover that the Resolution changed back to UNRESOLVED. Therefore, it appears that there was a bug in JIRA, that the code was being used to fix. The newer versions of JIRA do not have this bug, so the code is needed anymore.

Thank you all for the help.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

migration

jira-software