Platform notice: Server and Data Center only. This article only applies to Atlassian products on the server and data center platforms.
This knowledge base article describes an example of scenario where the project list page accessed from Top Bar > Projects > View All Projects takes a very long time to load (for example > 20s).
Jira 8.0.0 and above.
- When loading the Project list page while having the Network tab from the Browser Developer tool opened, we can see that one of the HTTP request which is loading a batch.js file takes a very long time to load (10-20 seconds), due to the big size of the file (several MBs):
In the example above, the batch.js file is loaded from the URL below:
- When running on a fresh vanilla Jira instance without any 3rd party add-on installed, or when entering plugin safe mode, we can see that the same file batch.js loads much faster (a few milliseconds) thanks to its very small size (a few KBs):
- Download the content of the problematic batch.js file as a temporary file on your local machine, which is possible by:
- Collecting a HAR file using the browser development tool.
- Clicking on the HTTP request from the Network tab and then clicking on the Response tab and saving its content to a text file:
For example, any key starting with the below string is coming from the ScriptRunner add-on:
/* module-key = 'com.onresolve.jira.groovy.groovyrunner ...
For example, any key starting with the below string is coming from the OrgWise-Organization and Report for Jira add-on:
/* module-key = 'com.shdsd.plugin.organizationPro ...
- You may also run the following command on Linux terminal to have an overview of which plugins are contributing on your batch.js response:
It also has an example response showing multiple plugins. From the results of your command, you could disable the respective plugins one at a time if plugin safe mode is not possible.
grep "module-key" contents_from_batch_js_response.txt | grep -v "com.atlassian\|jira.webresources\|com.pyxis.greenhopper.jira" | cut -d ':' -f1 | cut -d ' ' -f4 |sort | uniq -c | sort -nr 98 'com.okapya.jira.checklist 43 'com.almworks.jira.structure 25 'com.spartez.jira.plugins.jiraplanningpoker 17 'com.onresolve.jira.groovy.groovyrunner 14 'com.obss.plugin.time-in-status 11 'com.almworks.structure.gantt 6 'com.hascode.plugin.jira-quick-subtasks 5 'com.thinktilt.proforma.add-on 3 'com.intenso.jira.plugins.jsd-extender 2 'com.midori.jira.plugin.betterexcel 2 'com.googlecode.jira-suite-utilities 1 'com.testrail.jira.testrail-plugin 1 'com.resolution.atlasplugins.samlsso.Jira 1 'com.porzelt.jira.darktheme.DarkTheme
- Try to delete the scripts coming from these add-on keys, save the local file batch.js, and check if the size of the file decreased drastically. If that's the case, then it is an indication that the add-ons from which you deleted the scripts were the ones contributing to the big size of the batch.js file, and consequently the slow loading of the project list page.
- Alternatively, you can also confirm that the page loads faster, or that the size of batch.js file is smaller by either entering plugin safe mode, or disabling the add-ons identified in that file.
- Simplifying the code configured with these add-ons.
- Reaching out to the support teams responsible for these add-ons, since 3rd party add-ons fall outside of Atlassian support.
Was this helpful?Yes Provide feedback about this article