Known major problems with 3rd party apps in Jira

Still need help?

The Atlassian Community is here for you.

Ask the community


In order to prevent problems and downtime for clients, we would like to notify them about possible major issues with 3rd party apps (add-ons, plugins) in Jira

NOTE: As with all software, the best practice is to perform upgrades during off-peak hours. Additionally, ensure the environment is backed-up before executing the upgrade.


(tick) : Identified problem has been fixed. The suggestion is to upgrade to the corresponding app version.

(warning) : Problem is partially fixed, or the Jira Admin should be aware of the potential consequences of the app's functioning.

(error) : Issue persists. No known fix yet.

StatusVendor - PluginProblemAffected VersionUpdate toNotes

Adaptavist - ScriptRunner

Innovalog - JMWE

High memory consumptionAllNone

Using a Groovy script to call with a JQL that fetches too many issues leads to high memory consumption.

Either prevent such large-result JQL to be executed or use searchCount(...) if only the JQL result count matters. This is not an App issue — the App and Jira are behaving exactly as expected of them: loading many issues into the memory.

See related KB on Jira becomes unresponsive occasionally and logs several Full GC events.


Adaptavist - ScriptrunnerStackOverflowException5.3.26+5.5.2

There are some versions of ScriptRunner that has the issue, the preferable option would be to avoid using Agile JQL functions in card colour queries for the time being.


Adaptavist - ScriptrunnerClassloader lock contention4.0 -

A high number of calls to behaviours API (/rest/scriptrunner/behaviours/latest/validators.json) is causing classloader contention.
This is due to parsing behaviors configuration and executing createSaxParserFactory for each request.

(tick)Adaptavist - ScriptrunnerReindexing timepre performance of indexers for JQL functions (issueFunction custom field) has 20% improvement in indexing time. The improvements have been released as part of ScriptRunner 6.9.0.


The Plugin People - Enterprise Email Handler for Jira (JEMH)Too many threads running

purgeAuditHistory, that leads to OOM

2.4.x, 2.5.x2.4.4, 2.5.5

 1,500+ threads blocked on JEMH

Click here to expand...
java.lang.Thread.State: BLOCKED (on object monitor)
- waiting to lock <0x00000006c6f0a8a0> (a
(tick)The Plugin People - Enterprise Email Handler for Jira (JEMH)Expensive creation of JAXB Contexts leads to "OutOfMemory: Compressed Class Space" event, and eventually, Jira crashes.2.7.473.3.18
  • java.lang.OutOfMemoryError: Compressed class space visible in catalina.out
  • "Full GC (Last ditch collection)" visible in GC logs
2020-06-17T21:23:03.300+0100: 635045.200: [Full GC (Last ditch collection)  4431M->4407M(18G), 9.4323063 secs]
   [Eden: 0.0B(10.0G)->0.0B(10.0G) Survivors: 0.0B->0.0B Heap: 4431.1M(18.0G)->4407.6M(18.0G)], [Metaspace: 3185248K->3180537K(3268608K)]


META-INF KFT - Email This IssueHigh memory usage7.x7.1.0.17No cache clean-up for JiraAuthenticationContextImpl, which leads to leaking$QueryCacheLiteralsKey in ThreadLocals


META-INF KFT - Email This IssuePotential slow memory leak, leaking Velocity Object instances. and earlier


The plugin was using a Jira API that should be deprecated, the issue is fixed in plugin version JRASERVER-69457 - Getting issue details... STATUS

Version also have the leak, users should downgrade to

(warning)Xpand IT – XporterHigh memory usage/OOMAllNoneHeavy GC problems due to large memory pressure in JVM heap, caused by user action: export ALL issues using Xporter plugin. URL <Jira>/sr/com.xpandit.plugins.jiraxporter:xporter-currentfield-xlsx/temp/SearchRequest.xlsx


Xpand IT - XrayHigh memory usage/OOM3.

JQL function TestsWithoutTestExecution are potentially loading all Tests from a project. See

To workaround this, disable JQL module "testsWithReqVersion"


Xpand IT - XrayUpon upgrading from 3.1.x, index size increase significantly and high memory pressure3.2.0 -

Upon upgrade from 3.1.x to 3.2.x index size increases significantly and high CPU usage is observed. If upgrading from Xray 3.1.x, ensure you upgrade to the most recent version. Contact Xray support with any questions.

(tick)Xpand IT - XrayHigh memory / OOM3. bug that causes all issues to be loaded through JQL, causing large memory pressure.


J-Tricks - JQL Tricks


StackOverflowError caused by JQL LinkedIssueInFilter. Correspond threads are killed by JVM leaving application in corrupted state.

(error)Zephyr - ZephyrHigh memory usage/OOMAllNoneHeavy GC problems due to large memory pressure in JVM heap, caused by JQL function testsWithoutExecution(). Please avoid any searches of the format ie "project = <project 
name> AND issue not in testsWithoutExecution()" in you search pages. Idea of this JQL was to return all Testcases that are not assigned to any Cycle (in short does not have execution).
(tick)Zephyr - Zephyr

Node startup time increased significantly

Performance during the SYNC operation whenever a node is restarted has been improved in 4.0.6. This will significantly improve Zephyr startup time on restart.

(tick)Tempo - Tempo TeamsHuge database query count3.10.08.14

With Tempo teams installed, the Tempo code seems to be trying to verify some permissions from the table: "AO_AEFED0_PROGRAM".

The below query is executed many many times, ( thousands of time in some cases) and could be logged with set to trace:


This could cause Jira issue operations to get delayed for users who are impacted with this Tempo functionality.


Tempo -

Tempo Timesheets

Performance degradation due to frequent cache flushes10.18.5hotfix 10.18.6

Thread Dumps shows multiple threads waiting for a cache:

com.atlassian.jira.cache.DeferredReplicationCache$$Lambda$403/1522086636.get(Unknown Source)
(error)AM UtilsHigh Memory Usage/OOM1.3.21NoneThe issuesSubtasks (IssuesSubtasksJQL) function which returns a list of issues that are subtasks of all issues in the specified JQL query causes high memory usage or OOM error.
(warning)Git Integration for Jira - BigBrassBandHigh disk space consumption.

All versions

High disk space usage on both jira_home/caches/indexes and jira_home/data. Contact for advice on reducing the number of connected repositories. Screen-sharing support available.

Git Integration for Jira clones repositories to the Jira Server/Data Center instance then indexes the repositories to link commits, branches, and pull requests to Jira issues. Depending on number of repositories configured, size of repositories (commits, branches and tags), storage size of repositories, and other factors - the disk space required may require attention. Contact BigBrassBand support for strategies to reduce disk space usage.


JEditor - Rich Text Editor for Jira

Mention notifications are not triggered.3.0.9+
Notifications for mentions aren't triggered when using 'batching email notifications' and the JEditor renderer on the comment field. The vendor is aware of this issue and intends to have a fix for this in the next two weeks (as of 8/23/19). As a workaround, disable batching email notifications until this problem is fixed by the vendor.
(warning)Agile Reports and GadgetsHigh memory usage/OOM2.1.0NonePlugin developers have identified that the code for a functionality that works with JQL searches could cause high memory pressure and eventually lead to an OOM. Customer mentioned that after the issue started after they've upgraded to 2.1.0 and, once downgrading it back to 1.7.6, it has not occurred anymore. The developers are currently working on a permanent fix.
(warning)Exalate - IdalkoHigh memory usage/OOM

Script specific problem, not based on its versions. Check if the following script is causing an infinite loop, for example, a transition existed from the current status to itself.




High CPU utilisation3. Jeditor was impacting the CPU utilisation heavily. It bring the CPU utilisation to more then 75% on the machine. The Jeditor rendering a page was showing up on all threads consuming a high CPU.
(warning)Enhancer pluginHigh Memory Usage/OOM

subTasksByFieldInMainTask JQL function can use up a large memory and caused an OOME.
Workaround is to disable the plugin.jep:jep-jql-subtasksbyfieldinmaintask module
(error)Timesheet Reports and GadgetsHigh Memory utilization / Back to back Full GCs3.3.13
Review heap dump
(tick)ALM Works - StructureEditing or creating a sub-task issue does not work. UI shows spinning icon but never completes.6.0 and 6.0.1  6.1 Issue is intermittent per ALM works. HAR file will show a POST to /rest/webResources/1.0/resources failing with either no status code or a 404.

Issue Templates for Jira

Inline edit mode will throw a JavaScript error.


When you open an issue on the board in the Inline issue mode and try to edit after you click update, you'll see a JS error:

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

Exception: Uncaught TypeError: Cannot read property 'length' of undefined
(tick)Extension for Jira Service ManagementLow Jira performance with high load page times6.

Jira page load times are very long (i.e. loading an issue).

According to Deviniti, this is caused by recently implemented approach of a new feature - Rich Text custom field. The plugin imports this custom field on customer portal only when it is filled and the value for specific. Unfortunately the same was not applied to Jira issue view and as a result Rich text custom field is imported even if it isn’t used in a loaded issue.

(tick)Query Issues Custom FieldsHigh Memory Usage/OOM2.2.14Latest

Large memory consumption was seen on ru.andreymarkelov.atlas.plugin.qcf.field.LinkerMultiField.getVelocityParameters and caused Jira to hit OutOfMemoryError.

Issue was no longer reproducible since updating the plugin to the latest version.

(tick)CRM PluginHigh Memory Usage/OOM6.6.0-556497.2.8-55889

The issue happens when a CRM user clicks a "Link to existing Jira issue" custom button on their CRM screen and enters for the Issue Key the text "-25363" (example). The hyphen at the beginning of a word means to exclude matches that include the word (all issues except 25363), which means that a large result set can be retrieved.

A fix has been released in latest version of the plugin that will ignore such characters since we assume that CRM users won't expect hyphens and plus-signs to work this way.

(tick)BigPicture - Project Management & PPMSevere performance problems, taking more than 10 seconds to load an issue or to navigate through pages, some 504 timeouts while using the Home/Overview.8.0.0 -

Loading an issue (IssueView) taking more than 10 seconds to complete after upgrading the BigPicture plugin to version 8.0.0 to 8.0.3.

Fix has been releases by plugin vendor (SoftwarePlant) included in version 8.0.4

(error)In-App & Desktop Notifications for JiraThere were tens of thousands of user sessions by multiple users exhausting Jira resources and all hitting /servlet/nfj/PushNotification endpointPluguin version: 2.0.2_J8
  • We'd restart the server and the moment it's up there would be sometimes 50K sometimes 80K user sessions active on the server. This is in contrary to like 50/100 sessions on regular days
  • Checking the access logs showed each user was sending 10s of thousands of requests all on /servlet/nfj/PushNotification endpoint

Notification Assistant for Jira - Email

Blank screen when opening WebHooks admin page, also a gray "create" webhook button7.

in atlassian-jira.log, you will see a WARN message like this:

/_/download/contextbatch/css/atl.plugins.webhooks.admin,atl.admin,jira.admin,,,-_super/batch.css [webresource] error in `Content.writeTo` for com.riadalabs.jira.plugins.notificationassistant:add_js_css_resource/title-7.0.0.css
java.lang.RuntimeException: Cannot read resource ../frontend/src/components/nafj-components/title/title.css
(tick)Email This IssueFail to delete subtasks and linked issues with an index related message

When trying to delete subtasks or linked issues you will see an error like this in the UI:

Technical details
 Log's referral number: 16e9d49-6454-4v29-56az-f0a432314730

 Referer URL: []

com.atlassian.jira.index.IndexingFailureException: Indexing completed with 1 errors
 com.atlassian.jira.index.IndexingFailureException: Indexing completed with 1 errors
 at com.atlassian.jira.index.AccumulatingResultBuilder$CompositeResult.await( [classes/:?]
 at com.atlassian.jira.issue.index.DefaultIndexManager.obtain( [classes/:?]
 at com.atlassian.jira.issue.index.DefaultIndexManager.await( [classes/:?]
 at com.atlassian.jira.issue.index.DefaultIndexManager.executeWithIndexLock( [classes/:?]

If not possible to upgrade to the version that contains the fix, you can follow workaround steps as noted here:

(tick)Spartez SoftwareMissing Customer Portal menus on Jira Service Management when loading Chat for Service Management1.7.71.8

Menus will not load and from the web console we can detect errors to render the plugin elements:

The resource from “$calendarResource” was blocked due to MIME type (“text/html”) mismatch (X-Content-Type-Options: nosniff). 
Loading failed for the <script> with source “$calendarResource”.
Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user’s experience. For more help batch.js:69:74525
Uncaught ReferenceError: spartezSupportChat is not defined

(tick)Checklist for JiraHigh database utilisation5.

Many threads in Jira are consumed by com.okapya.jira.customfields.ChecklistBuilder.getLockedGlobalItems reading the database, which results in severe performance degradation.

Solution: Upgrade the plugin to the fix version listed.

(error)Adaptavist - ScriptRunnerBroken integration between Automation for Jira and Profields - Jira Project TrackingAllNone

When using the integration between Automation for Jira and Profields - Jira Project Tracking plugins the user received the following error:

Disabled third party extension for Automation for Jira?

The root cause is ScriptRunner breaks the integration between these 2 plugins. Once ScriptRunner is either uninstalled or disabled, it starts working again. Adaptavist is tracking a bug in their portal: SRJIRA-4357

Last modified on Apr 6, 2021

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.