Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

After upgrading to 8.22, screens loaded under Project menu are disabled

Hi,  I upgraded from Jira Core server 7.1.7 to 8.22.  Since the upgrade, any attempt to open a project under the Projects menu results in a completely greyed out screen.  

The first issue in the list loads, but the entire screen (apart from the top and left navs) is greyed-out.  Loading issues through the Issues / Search screen works fine.

This javascript error is triggered from batch.js:

Uncaught TypeError: Cannot set properties of undefined (setting 'bootstrap')
at D.n.initialize (batch.js?baseurl-check-resources=true&healthcheck-resources=true&jira.create.linked.issue=true&locale=en-US&richediton=true:41042:2535)
at e.View (batch.js?locale=en-US:740:14114)
at D.n [as constructor] (batch.js?locale=en-US:740:23495)
at new D.n (batch.js?locale=en-US:740:23495)
at eval (eval at globalEval (batch.js?locale=en-US:158:1085), <anonymous>:8:34)
at eval (eval at globalEval (batch.js?locale=en-US:158:1085), <anonymous>:14:6)
at eval (<anonymous>)
at Function.globalEval (batch.js?locale=en-US:158:1085)
at ye (batch.js?locale=en-US:184:1380)
at u.fn.init.append (batch.js?locale=en-US:189:1099)


Does anybody know how to work around this or what the cause could be?  It's my first time posting here so let me know if further info is required.

Thank you,




1 answer

1 accepted

1 vote
Answer accepted
Dirk Ronsmans
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Aug 29, 2022

Hey @pascal and welcome to the community!

Have you tried it without any apps/add-ons enabled?

Often these things are app related and one of the apps you have might not be compatible. So to rule that out i'd suggest to disable all apps you have installed and enable them one by one to test.

Thanks for putting me on the right track!  Turns out I had to re-install Jira Service Management and Jira Software.  I guess they were outdated after the upgrade.  Anyway that resolved the issue. 

Thanks for answering and have a great day.

Like Dirk Ronsmans likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events