I'm getting an exception on the backlog page of an agile board after upgrading Jira Core from 7.4.1 to 7.7.1. The exception stack trace is shown below. I haven't yet seen an actual problem using a board yet, but I assume I will eventually. Suggestions for further triage would be helpful. Error message and stack trace, with identifying information from my server removed (atlassian code references untouched): An error occurredHide… Please try refreshing the page, or contact your administrator / Atlassian Support if the problem continues. Details * * Exception: Uncaught TypeError: c.isEpicsPanelEnabled is not a function * Resource: /download/contextbatch/js/greenhopper-rapid-non-gadget,atl.general,gh-rapid,jira.project.sidebar,com.atlassian.jira.projects.sidebar.init,jira.global,jira.general,-_super/batch.js?agile_global_admin_condition=true&healthcheck-resources=true&is-server-instance=true&is-system-admin=true&jag=true&jaguser=true&jira-nps-enabled=true&locale=en-US&nps-acknowledged=true&nps-not-opted-out=true&richediton=true * Line: 9895 * Column: 589 Environment Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36 Stack trace * TypeError: c.isEpicsPanelEnabled is not a function * at e (/download/contextbatch/js/greenhopper-rapid-non-gadget,atl.general,gh-rapid,jira.project.sidebar,com.atlassian.jira.projects.sidebar.init,jira.global,jira.general,-_super/batch.js?agile_global_admin_condition=true&healthcheck-resources=true&is-server-instance=true&is-system-admin=true&jag=true&jaguser=true&jira-nps-enabled=true&locale=en-US&nps-acknowledged=true&nps-not-opted-out=true&richediton=true:9895:589) * at d.f [as filterOutGHEpics] (/download/contextbatch/js/greenhopper-rapid-non-gadget,atl.general,gh-rapid,jira.project.sidebar,com.atlassian.jira.projects.sidebar.init,jira.global,jira.general,-_super/batch.js?agile_global_admin_condition=true&healthcheck-resources=true&is-server-instance=true&is-system-admin=true&jag=true&jaguser=true&jira-nps-enabled=true&locale=en-US&nps-acknowledged=true&nps-not-opted-out=true&richediton=true:9895:502) * at d.g [as reset] (/download/contextbatch/js/greenhopper-rapid-non-gadget,atl.general,gh-rapid,jira.project.sidebar,com.atlassian.jira.projects.sidebar.init,jira.global,jira.general,-_super/batch.js?agile_global_admin_condition=true&healthcheck-resources=true&is-server-instance=true&is-system-admin=true&jag=true&jaguser=true&jira-nps-enabled=true&locale=en-US&nps-acknowledged=true&nps-not-opted-out=true&richediton=true:9895:359) * at d [as parse] (/download/contextbatch/js/greenhopper-rapid-non-gadget,atl.general,gh-rapid,jira.project.sidebar,com.atlassian.jira.projects.sidebar.init,jira.global,jira.general,-_super/batch.js?agile_global_admin_condition=true&healthcheck-resources=true&is-server-instance=true&is-system-admin=true&jag=true&jaguser=true&jira-nps-enabled=true&locale=en-US&nps-acknowledged=true&nps-not-opted-out=true&richediton=true:3103:1191) * at Object.a.success (/download/contextbatch/js/greenhopper-rapid-non-gadget,atl.general,gh-rapid,jira.project.sidebar,com.atlassian.jira.projects.sidebar.init,jira.global,jira.general,-_super/batch.js?agile_global_admin_condition=true&healthcheck-resources=true&is-server-instance=true&is-system-admin=true&jag=true&jaguser=true&jira-nps-enabled=true&locale=en-US&nps-acknowledged=true&nps-not-opted-out=true&richediton=true:2887:125) * at j /download/contextbatch/js/_super/batch.js?locale=en-US:63:58) * at Object.fireWith [as resolveWith] (/download/contextbatch/js/_super/batch.js?locale=en-US:64:361) * at d (/download/contextbatch/js/_super/batch.js?locale=en-US:189:292) * at XMLHttpRequest.b (/download/contextbatch/js/_super/batch.js?locale=en-US:201:149)

I'm definitely not on cloud. OK, I guess what I missed is that "Jira Software" is a plugin that you download, and not part of the base install package. When I went to Jira Adminstration >> Applications page, there was a big red warning there that I was running Jira Software 7.4.1 on Jira Core 7.7.1. It had to be something that stupid simple, of course. I don't understand your reference to the JIRA defect above, because I have both Agile boards and Kanban boards in my project now.

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

Exception on Agile board after upgrading Jira from 7.4.1 to 7.7.1

Eric Wittle

I'm getting an exception on the backlog page of an agile board after upgrading Jira Core from 7.4.1 to 7.7.1. The exception stack trace is shown below. I haven't yet seen an actual problem using a board yet, but I assume I will eventually. Suggestions for further triage would be helpful.

Error message and stack trace, with identifying information from my server removed (atlassian code references untouched):

An error occurredHide…

Please try refreshing the page, or contact your administrator / Atlassian Support if the problem continues.

Details

- Exception: Uncaught TypeError: c.isEpicsPanelEnabled is not a function
- Resource: /download/contextbatch/js/greenhopper-rapid-non-gadget,atl.general,gh-rapid,jira.project.sidebar,com.atlassian.jira.projects.sidebar.init,jira.global,jira.general,-_super/batch.js?agile_global_admin_condition=true&healthcheck-resources=true&is-server-instance=true&is-system-admin=true&jag=true&jaguser=true&jira-nps-enabled=true&locale=en-US&nps-acknowledged=true&nps-not-opted-out=true&richediton=true
- Line: 9895
- Column: 589

Environment

Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36

Stack trace

TypeError: c.isEpicsPanelEnabled is not a function
at e (/download/contextbatch/js/greenhopper-rapid-non-gadget,atl.general,gh-rapid,jira.project.sidebar,com.atlassian.jira.projects.sidebar.init,jira.global,jira.general,-_super/batch.js?agile_global_admin_condition=true&healthcheck-resources=true&is-server-instance=true&is-system-admin=true&jag=true&jaguser=true&jira-nps-enabled=true&locale=en-US&nps-acknowledged=true&nps-not-opted-out=true&richediton=true:9895:589)
at d.f [as filterOutGHEpics] (/download/contextbatch/js/greenhopper-rapid-non-gadget,atl.general,gh-rapid,jira.project.sidebar,com.atlassian.jira.projects.sidebar.init,jira.global,jira.general,-_super/batch.js?agile_global_admin_condition=true&healthcheck-resources=true&is-server-instance=true&is-system-admin=true&jag=true&jaguser=true&jira-nps-enabled=true&locale=en-US&nps-acknowledged=true&nps-not-opted-out=true&richediton=true:9895:502)
at d.g [as reset] (/download/contextbatch/js/greenhopper-rapid-non-gadget,atl.general,gh-rapid,jira.project.sidebar,com.atlassian.jira.projects.sidebar.init,jira.global,jira.general,-_super/batch.js?agile_global_admin_condition=true&healthcheck-resources=true&is-server-instance=true&is-system-admin=true&jag=true&jaguser=true&jira-nps-enabled=true&locale=en-US&nps-acknowledged=true&nps-not-opted-out=true&richediton=true:9895:359)
at d [as parse] (/download/contextbatch/js/greenhopper-rapid-non-gadget,atl.general,gh-rapid,jira.project.sidebar,com.atlassian.jira.projects.sidebar.init,jira.global,jira.general,-_super/batch.js?agile_global_admin_condition=true&healthcheck-resources=true&is-server-instance=true&is-system-admin=true&jag=true&jaguser=true&jira-nps-enabled=true&locale=en-US&nps-acknowledged=true&nps-not-opted-out=true&richediton=true:3103:1191)
at Object.a.success (/download/contextbatch/js/greenhopper-rapid-non-gadget,atl.general,gh-rapid,jira.project.sidebar,com.atlassian.jira.projects.sidebar.init,jira.global,jira.general,-_super/batch.js?agile_global_admin_condition=true&healthcheck-resources=true&is-server-instance=true&is-system-admin=true&jag=true&jaguser=true&jira-nps-enabled=true&locale=en-US&nps-acknowledged=true&nps-not-opted-out=true&richediton=true:2887:125)
at j /download/contextbatch/js/_super/batch.js?locale=en-US:63:58)
at Object.fireWith [as resolveWith] (/download/contextbatch/js/_super/batch.js?locale=en-US:64:361)
at d (/download/contextbatch/js/_super/batch.js?locale=en-US:189:292)
at XMLHttpRequest.b (/download/contextbatch/js/_super/batch.js?locale=en-US:201:149)

Accepted answers

All comments

Maarten Cautreels

Hi Eric,

It's a client side error you're getting. I just checked on my JIRA 7.7.1 and my Kanban backlog works perfectly fine. Can you please clear your cache or try another browser just to make sure JIRA isn't using an older version of the frontend sources?

A second option is described in a Knowledge Base Article. It could be that you're JIRA Core is not on the same version as your JIRA Software.

Best,

Maarten

Eric Wittle

Cleared the cache, restarted the browser, still get the same error. I read that knowledge base article, but I'm running only Jira Core from that server. I do have Bitbucket running in a separate instance, but AFAIK that isn't what the KB article is referring to.

Eric Wittle

P.S. I only use Jira in Safari & Chrome. Just to be sure, I started Firefox and logged in from there, same error. It is highly unlikely that it is a caching issue, given that I'm pretty sure I never accessed Jira from Firefox before.

Danyal Iqbal

The version of JIRA Software is incompatible with the current version of JIRA Core.

KellyW

Hi Maarten,

As mentioned earlier, sometimes "TypeError: c.isEpicsPanelEnabled is not a function" error is triggered by when you are running incompatible JIRA Software release, even thought both JIRA Core and JIRA Software seems running on same release from JIRA Administration >> Applications >> Versions & licenses page.

I would suggest re-install JIRA Software by downloading the relevant OBR from the marketplace and upload it on JIRA Administration >> Applications >> Version & licenses page. Once done, restart JIRA, do a re-index and let us know if the problem persist.

Regards,

Kelly

Eric Wittle

Thanks for the reference to the versions and licenses page. Once I visited there, the issue of Jira software version being different than Jira core showed up immediately. I guess I don't understand why that isn't a warning that is more visible.

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-software