Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Issues Page No Longer Loads in Jira 8

Iain Willis February 15, 2019

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)

1 answer

1 accepted

0 votes
Answer accepted
Iain Willis February 15, 2019

I found the problem - it was an incompatible plugin, disabling it restored the functionality.

Craig Castle-Mead
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 21, 2019

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

Like Ahmed Hassanen likes this
Iain Willis February 25, 2019

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

Like Craig Castle-Mead likes this

Suggest an answer

Log in or Sign up to answer