This page is failing to load after upgrading to Jira 8.
Does anyone know of a solution to this issue?
I get the following in the javascript console:
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-GB&richediton=true&user-logged-in=true&whisper-enabled=true:3205 TypeError: a.isFullScreenIssueVisible is not a function
at Object.isFullScreenIssueVisible (batch.js?locale=en-GB:2949)
at HTMLDocument.<anonymous> (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-GB&richediton=true&user-logged-in=true&whisper-enabled=true:595)
at c (batch.js?locale=en-GB:65)
at Object.add [as done] (batch.js?locale=en-GB:65)
at E.fn.init.E.fn.ready (batch.js?locale=en-GB:65)
at c.fn.init.E.fn.init (batch.js?locale=en-GB:65)
at new c.fn.init (batch.js?locale=en-GB:83)
at E (batch.js?locale=en-GB:54)
at Object.n.documentReadyInit (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-GB&richediton=true&user-logged-in=true&whisper-enabled=true:595)
at 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-GB&richediton=true&user-logged-in=true&whisper-enabled=true:3209
b.oe @ 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-GB&richediton=true&user-logged-in=true&whisper-enabled=true:3205
batch.js?locale=en-GB:2949 Uncaught (in promise) TypeError: a.isFullScreenIssueVisible is not a function
at Object.isFullScreenIssueVisible (batch.js?locale=en-GB:2949)
at HTMLDocument.<anonymous> (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-GB&richediton=true&user-logged-in=true&whisper-enabled=true:595)
at c (batch.js?locale=en-GB:65)
at Object.add [as done] (batch.js?locale=en-GB:65)
at E.fn.init.E.fn.ready (batch.js?locale=en-GB:65)
at c.fn.init.E.fn.init (batch.js?locale=en-GB:65)
at new c.fn.init (batch.js?locale=en-GB:83)
at E (batch.js?locale=en-GB:54)
at Object.n.documentReadyInit (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-GB&richediton=true&user-logged-in=true&whisper-enabled=true:595)
I found the problem - it was an incompatible plugin, disabling it restored the functionality.
Hey Iain,
do you mind sharing which addon (and version) it was that was causing this issue?
May help others (including me) debug/resolve a similar issue in the future.
CCM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Craig,
Sure, it was the Tracking and Estimation for Jira plugin (com.adweb.estimations.estimationUpdate), which I see has just had an update and is now flagged as compatible with Jira 8.
Iain
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.