Jira freezes and becomes unresponsive while Editing the issues
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Jira freezes and becomes unresponsive while Editing the issues. Screens don't load and user requests aren't completed.
Diagnosis
The following error can be observed on the browser's console log when trying to edit a JIRA Software issue.
VM2455:6 company_value = 3rdParty VM2455:11 Uncaught TypeError: Cannot read properties of null (reading 'style') at eval (eval at globalEval (batch.js?locale=en-US:43:1085), <anonymous>:11:14) at eval (<anonymous>) at Function.globalEval (batch.js?locale=en-US:43:1085) at ye (batch.js?locale=en-US:69:1380) at u.fn.init.append (batch.js?locale=en-US:74:1099) at e.fn.<computed> (batch.js?agile_global_admin_condition=true&baseurl-check-resources=true&healthcheck-resources=true&jag=true&jaguser=true&jira.create.linked.issue=true&locale=en-US&richediton=true:24050:5182) at b.fn.<computed> [as append] (batch.js?agile_global_admin_condition=true&baseurl-check-resources=true&healthcheck-resources=true&jag=true&jaguser=true&jira.create.linked.issue=true&locale=en-US&richediton=true:145972:2056) at u.fn.init.<anonymous> (batch.js?locale=en-US:74:2187) at F (batch.js?locale=en-US:54:26034) at u.fn.init.html (batch.js?locale=en-US:74:1868) eval @ VM2455:11 |
Cause
There is a script on one of the custom fields which is not correctly structured. An infinite loop in the custom javascript was causing the issue.
Workaround
Take proper backup, and remove those scripts from the custom field to prevent the problem from happening.
Solution
Evaluate all the scripts embedded in the custom field configuration and perform some tests based on trial & error to identify the exact script which is causing the problem.
In this example, the script was coming from the Company Value custom field's default value. It appears that this script is having an Infinite loop and is causing the javascript error. Clearing the javascript fixes the problem.
Was this helpful?