Known major problems with 3rd party apps in Jira
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.
: Identified problem has been fixed. The suggestion is to upgrade to the corresponding app version.
: Problem is partially fixed, or the Jira Admin should be aware of the potential consequences of the app's functioning.
: Issue persists. No known fix yet.
|Status||Vendor - Plugin||Problem||Affected Version||Update to||Notes|
|High memory consumption||All||None|
Using a Groovy script to call com.atlassian.jira.issue.search.SearchProvider.search(...) 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 - Scriptrunner||StackOverflowException||5.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 - Scriptrunner||Classloader lock contention||4.0 - 188.8.131.52||5.5.10|
A high number of calls to behaviours API (/rest/scriptrunner/behaviours/latest/validators.json) is causing classloader contention.
|Adaptavist - Scriptrunner||Reindexing time||pre 6.9||6.9.0||The 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.x||2.4.4, 2.5.5|
1,500+ threads blocked on JEMH
Click here to expand...
|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.47||3.3.18|
|META-INF KFT - Email This Issue||High memory usage||7.x||184.108.40.206||No cache clean-up for JiraAuthenticationContextImpl, which leads to leaking com.atlassian.jira.bc.issue.search.QueryCacheImpl$QueryCacheLiteralsKey in ThreadLocals|
|META-INF KFT - Email This Issue||Potential slow memory leak, leaking Velocity Object instances.|
220.127.116.11 and earlier
|Xpand IT – Xporter||High memory usage/OOM||All||None||Heavy 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 - Xray||High memory usage/OOM||3.1.3||3.1.4|
JQL function TestsWithoutTestExecution are potentially loading all Tests from a project. See https://jira.xpand-addons.com/browse/XRAY-2868
To workaround this, disable JQL module "testsWithReqVersion"
|Xpand IT - Xray||Upon upgrading from 3.1.x, index size increase significantly and high memory pressure||3.2.0 - 3.2.2||3.2.3|
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.
|Xpand IT - Xray||High memory / OOM||3.5.3||3.5.4+||A 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.
|Zephyr - Zephyr||High memory usage/OOM||All||None||Heavy 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).
|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.
|Tempo - Tempo Teams||Huge database query count||3.10.0||8.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 net.java.ao.sql set to trace:
This could cause Jira issue operations to get delayed for users who are impacted with this Tempo functionality.
|Performance degradation due to frequent cache flushes||10.18.5||hotfix 10.18.6|
Thread Dumps shows multiple threads waiting for a cache:
|AM Utils||High Memory Usage/OOM||1.3.21||None||The 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.|
|Git Integration for Jira - BigBrassBand||High disk space consumption.|
High disk space usage on both jira_home/caches/indexes and jira_home/data. Contact email@example.com 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.
|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.|
|Agile Reports and Gadgets||High memory usage/OOM||2.1.0||None||Plugin 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.|
|Exalate - Idalko||High 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 utilisation||3.1.1||3.2.2||The 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.|
|Enhancer plugin||High Memory Usage/OOM|
Workaround is to disable the
|Timesheet Reports and Gadgets||High Memory utilization / Back to back Full GCs||3.3.13||Review heap dump|
|ALM Works - Structure||Editing 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.|
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:
|Extension for Jira Service Management||Low Jira performance with high load page times||6.9.1||6.9.2|
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.
|Query Issues Custom Fields||High Memory Usage/OOM||2.2.14||Latest|
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.
|CRM Plugin||High Memory Usage/OOM||6.6.0-55649||7.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.
|BigPicture - Project Management & PPM||Severe 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 - 8.0.3||8.0.4|
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
|In-App & Desktop Notifications for Jira||There were tens of thousands of user sessions by multiple users exhausting Jira resources and all hitting /servlet/nfj/PushNotification endpoint||Pluguin version: 2.0.2_J8|
|Blank screen when opening WebHooks admin page, also a gray "create" webhook button||7.0.0||7.0.4|
in atlassian-jira.log, you will see a WARN message like this:
|Email This Issue||Fail to delete subtasks and linked issues with an index related message||8.1.1||8.1.2-GA|
When trying to delete subtasks or linked issues you will see an error like this in the UI:
If not possible to upgrade to the version that contains the fix, you can follow workaround steps as noted here: https://metainf.atlassian.net/wiki/spaces/PLUG/pages/1393164352/Fix+issues+with+corrupt+index+state
|Spartez Software||Missing Customer Portal menus on Jira Service Management when loading Chat for Service Management||1.7.7||1.8|
Menus will not load and from the web console we can detect errors to render the plugin elements:
|Checklist for Jira||High database utilisation||5.0.5||5.0.6|
Many threads in Jira are consumed by
Solution: Upgrade the plugin to the fix version listed.
|Adaptavist - ScriptRunner||Broken integration between Automation for Jira and Profields - Jira Project Tracking||All||None|
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