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; } } }

Cannot Complete Issues after upgrading from version 4.4.5 to 6.4.40, nor in 7.0.1

James Shablow_5a7y89

I have been migrating the JIRA data for the company I work for from version 4.0.2 to the latest version. Although I have experienced many road blocks, today I was finally able to install and configure JIRA 4.0.2 on a test laptop, import the data from our old server, and upgrade to version 4.4.5 manually. There were several errors that seemed to be resolved by re-indexing. I testing creating, editing, and completing an issue, and everything worked fine. I then upgraded to version 6.4.40 using the in-line upgrade. I was testing that and discovered that I was unable to complete an issue, but am able to edit it. When I click on "Complete" the screen dims and a loading icon appears (shown below). I have tried waiting over 5 minutes, and the screen did not change. I was able to cancel the action with 'Esc'.

2018-07-09 16_11_18-[TP-81] Testing issue creation in JIRA version 6.4 - JIRA.png

Any thoughts? What might have gotten corrupted during the upgrade from 4.4.5 to 6.4.40?

Thanks.

EDIT 2018-7-10-0821: I've tried updating the workflow, but JIRA still gets stuck when I try to Complete the issue.

Accepted answers

James Shablow_5a7y89

Thank you all for the help. This issue was ultimately resolved when an Atlassian employee advised that the code is not native code. It turned out to be custom code that had been added to the Field Configuration Scheme to adjust for a bug that existed in the older version of JIRA, but no longer exists in more recent versions. Removing this custom code resolved the error.

The discussion can be found here.

All comments

Sloan N_ B_

Hi James

Can you check your browsers dev-tools and look for errors in the console tab and the network tab when trying to complete the issue?

In Chrome for example open the dev-tools with F12 or Ctrl + Shift + I (Windows) or ⌥ + ⌘ + I (Mac).

Cheers
Niklas

James Shablow_5a7y89

Hey Niklas, below is a copy-paste of the errors:

Failed to load resource: the server responded with a status of 404 (Not Found)
1.gif Failed to load resource: the server responded with a status of 404 (Not Found)
batch.js:216 DEPRECATED - Dropdown constructor has been deprecated and will be removed in a future release. Use Dropdown2 instead. 
 at Object.exports.bindConfigDashboardDds (http://localhost:8080/s/5c513e4dfe8926ae9c3706a6a5a0dea8-CDN/en_US-l3h6im/70121/b6b48b2829824b869586ac216d119363/580f6d922253cb5eda78c1a2fa421f8c/_/download/contextbatch/js/_super/batch.js?atlassian.aui.raphael.disabled=true&locale=en-US:2899:1648)
(anonymous) @ batch.js:216
batch.js:216 DEPRECATED - Inline dialog constructor has been deprecated and will be removed in a future release. Use inline dialog 2 instead. 
 at HTMLDocument.<anonymous> (http://localhost:8080/s/c83d2c69af8b4764ab7bdc65bcb4c211-CDN/en_US-l3h6im/70121/b6b48b2829824b869586ac216d119363/373100e8acc5495dbacb1f3113b98c9d/_/download/contextbatch/js/jira.view.issue,jira.navigator.simple,jira.navigator.advanced,jira.navigator.kickass,atl.general,atl.global,jira.global,jira.general,-_super/batch.js?isAdmin=true&locale=en-US&user-logged-in=true:146:33)
(anonymous) @ batch.js:216
batch.js:216 DEPRECATED - Inline dialog constructor has been deprecated and will be removed in a future release. Use inline dialog 2 instead. 
 at JIRA.JiraSharePlugin.SharePluginDialog._initShareDialog (http://localhost:8080/s/c83d2c69af8b4764ab7bdc65bcb4c211-CDN/en_US-l3h6im/70121/b6b48b2829824b869586ac216d119363/373100e8acc5495dbacb1f3113b98c9d/_/download/contextbatch/js/jira.view.issue,jira.navigator.simple,jira.navigator.advanced,jira.navigator.kickass,atl.general,atl.global,jira.global,jira.general,-_super/batch.js?isAdmin=true&locale=en-US&user-logged-in=true:1968:6690)
(anonymous) @ batch.js:216
batch.js?isAdmin=true&locale=en-US&user-logged-in=true:335 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 selected="selected" value="6">
 Fixed
 </option>
 <option value="7">
 Won&#39;t Fix
 </option>
 <option value="8">
 Duplicate
 </option>
 <option value="9">
 Incomplete
 </option>
 <option value="10">
 UNRESOLVED
 </option>
 <option value="11">
 As Intended
 </option>
 </select>
 <a class="help-lnk" href="/secure/ShowConstantsHelp.jspa?decorator=popup#ResolutionTypes" title="Get local help about Resolution" data-helplink="local"><span class="aui-icon aui-icon-small aui-iconfont-help"></span></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) @ batch.js?isAdmin=true&locale=en-US&user-logged-in=true:335
batch.js:216 Downloading resources:
js!/s/2b15c5f5e27497e919914792f5c0137d-CDN/en_US-l3h6im/70121/b6b48b2829824b869586ac216d119363/01e2a9b167b4b92d8f1e3bb1beb2f952/_/download/contextbatch/js/com.atlassian.jira.plugins.jira-development-integration-plugin:devstatus-dialog-resources-ctx,-atl.general,-jira.navigator.advanced,-jira.navigator.simple,-atl.global,-jira.view.issue,-jira.global,-jira.navigator.kickass,-_super,-jira.general/batch.js?locale=en-US!order
css!/s/60dec57fe7c562b6c30061287ab9bec4-CDN/en_US-l3h6im/70121/b6b48b2829824b869586ac216d119363/01e2a9b167b4b92d8f1e3bb1beb2f952/_/download/contextbatch/css/com.atlassian.jira.plugins.jira-development-integration-plugin:devstatus-dialog-resources-ctx,-atl.general,-jira.navigator.advanced,-jira.navigator.simple,-atl.global,-jira.view.issue,-jira.global,-jira.navigator.kickass,-_super,-jira.general/batch.css
VM1733:2 Uncaught TypeError: Cannot set property 'onsubmit' of undefined
 at eval (eval at <anonymous> (batch.js:34), <anonymous>:2:27)
 at eval (<anonymous>)
 at batch.js:34
 at Function.globalEval (batch.js:34)
 at HTMLScriptElement.<anonymous> (batch.js:146)
 at Function.each (batch.js:35)
 at init.domManip (batch.js:145)
 at init.append (batch.js:140)
 at init.<anonymous> (batch.js:143)
 at Function.access (batch.js:38)

The network tab does not really provide any information besides the issue data (as Complete), the loading icon, a red asterisk, and "WorkflowUIDispatcher.jspa".

James Shablow_5a7y89

I started over again and upgraded to 5.2 once 4.4.5 was working fine. This issue also persists in this version. Both installs are 32-bit.

Cannot set property 'onsubmit' of undefined, in: <div class="field-group"

Any thoughts?

Sloan N_ B_

Hm, this doesn't looks like the errors I know.

Can you also go and check the Application-Logs of your Jira? Search for Error and Warnings with the used username and timestamps.

Matt Doar_tzgiej

Perhaps see if using the standard workflow for that issue/project makes any difference?

Also check the Network tab in the developer tools to see if you can tell which network call fails when you click Complete.

Mirek

@James Shablow- Do you only upgrade JIRA or also you are making sure of upgrading all other plugins/addons. Sometimes and old/not compatible addon can be the bottle neck. I did some time ago upgrade of Confluence from 2.x to 6.x and it was also frustrating but what is important - need to pay attention to details and things that changed between versions. That include version of Java, JDBC drivers.. database versions.. etc. everything need to be inline with what was supported in specific version. Reading upgrade notes for every version (of app and addons) is required and making sure that all upgrade tasks are executed (after upgrade), reindex is done .. etc. Check logs directly after upgrade (on first start). Those are most useful. If you can revert back to previous version and try upgrade again that is also a good way since sometimes you missed and important step and next time you see that the order also count.

James Shablow_5a7y89

The discussion can be found here.

Andy Heinzer

Cool - thanks for letting us know the solution here!

Welcome!

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

Quick Links

Find more posts tagged with

server

issue

migration

jira-software

jira-software-server

upgrade

error