Known issues with 3rd party apps in Jira
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
In order to prevent problems and downtime for clients, we would like to notify them about possible 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.
It's the vendors' responsibility to fix and inform what release fixes a given problem.
The information provided at the "Update to" is relayed to us by the vendors themselves.
The list is not complete, as it only contains issues reported by customers and vendors to Atlassian support. The issues and the plugins are not supported by Atlassian. Please contact the vendors for further details. See Atlassian Supported Plugins for more information.
Solution
: Identified problem has been fixed. The suggestion is to upgrade to the corresponding app version.
| Vendor - Plugin | Problem | Affected Version | Update to | Notes | |
|---|---|---|---|---|---|
| CollabSoft - Version & Component Sync for Jira | ProForma section on the Issue screen shows no data. | 3.0.0 | - | This is caused by a dependency collision between Version & Component Sync 3.0.0 and ProForma. Depending which app is loaded last, it'd be affected (Version & Component Sync can affect ProForma or vice-versa). Workaround: disable the app or reach out to CollabSoft for support on alternatives. When ProForma's impacted, the Forms section is empty even when expanded:
On the browser's console we see several messages from ProForma: "AMD module not loaded yet" and it never loads if the Version & Component Sync apps's enabled. | |
| Adaptavist - Scriptrunner for Jira | Automation queue is flooded with triggers from Assets Objects updates or creations. Regular Automation Rules may take hours to run because the queue was flooded. | Any with the modules enabled | ScriptRunner ships two triggers enabled by default:
They push to the automation queue at every Object update, potentially flooding the queue even if no Rule's making use of them. There's an improvement tracked by Adaptavist on SRJIRA-7291. | ||
| Xray Test Management for Jira | Adding/Removing/Updating Xray elements (Pre-condition, Test, Test Sets etc) in a Jira issue does not update Jira index |
| Confirmed bug by vendor: https://jira.getxray.app/browse/XRAY-9317 | ||
| Unexpected error. Code0 on loading an issue | 5.8.4 | 5.10 |
| |
| Adaptavist - Scriptrunner for Jira | StackOverflow Exception | 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 for Jira | Classloader lock contention | 4.0 5.5.9.1 | 5.6.1 | A high number of calls to behaviours API (/rest/scriptrunner/behaviours/latest/validators.json) is causing classloader contention. |
| Adaptavist - Scriptrunner for Jira | 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. |
| ALM Works - Structure | Editing or creating a sub-task issue does not work. UI shows spinning icon but never completes. | 6.0 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. |
| Better Excel Exporter for Jira | Cannot be enabled | 6.2.0 | 7.2.0 | Throws the error below in the logs: |
| | Bigbrass - Git Integration for Jira | Performance issue while accessing Git Repo | 4.0.2 | 4.0.5 | It takes more than 3 minutes to view Git Repositories |
| BigPicture - Project Management & PPM | Jira Index corruption (FileLock invalidated by an external force). | 8.21.0 | 8.25.0 | BigPicture jobs can corrupt Jira indexes due to the Index write.lock being tampered with ("FileLock invalidated by an external force"): Update BigPicture to the fixed version 8.25.0 or higher (ONE-85580). |
| 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 the plugin vendor (SoftwarePlant) included in version 8.0.4 |
| BigPicture - Project Management & PPM (Server) | "License is for an older version and maintenance period has expired" message and loss of app functionality after maintenance expiry, even though the perpetual license is still valid. | 8.6.3 and earlier | 8.6.4 | |
| BigTemplate - Export to PDF, Word, Excel (Server) | "License is for an older version and maintenance period has expired" message and loss of app functionality after maintenance expiry, even though the perpetual license is still valid. | 8.6.3 and earlier | 8.6.4 | |
| | Bobronix - JEditor - Rich Text Editor for Jira | 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. |
| Checklist for Jira | High database utilization | 5.0.5 | 5.0.6 | Many threads in Jira are consumed by Solution: Upgrade the plugin to the fixed version listed. |
| 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). A fix has been released in the 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. |
| Elements Connect | Automation for Jira shows a blank page at the "new action" step | Problematic version: 6.5.3 Automation for Jira: 7.3.3 | 6.5.6 | When creating a new rule:
|
| 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. 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. |
| Group Sign-Off: parallel Multi-Approvals | Above version 2.7.5-JIRA8 | Downgrading to 2.7.5-JIRA8 resolves the problem | Newer versions of the plugin interact negatively with Jira Service Management Customer Portal. When attempting to create a new ticket, the usual form fields do not load, rather, a spinner appears. The following error is logged to the JavaScript console | |
| Inline edit mode will throw a JavaScript error. | 7.13.x | 7.14 | 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: | |
| META-INF KFT - Email This Issue | High memory usage | 7.x | 7.1.0.17 | 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. | 7.1.1.16 and earlier | 7.1.1.17 | The plugin was using a Jira API that should be deprecated, the issue is fixed in plugin version 7.1.1.17. Version 7.1.1.18 also have the leak, users should downgrade to 7.1.1.17 |
| META-INF KFT - 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 |
| | Redirect to wrong URL upon Session timeout | 2.0.9 | 2.0.10 | Added option to configure additional Response endpoint for SAML Single Logout. | |
| 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: | |
| 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. The issue was no longer reproducible since updating the plugin to the latest version. |
| | Rixter AB - Integrations Hub for Jira | High memory consumption | 5.8.4 and lower | 5.9.0 | A misconfigured import (infinite loop) can create memory pressure and OOM event. Workaround: Configure the import to avoid the infinite loop. Solution to update to v5.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 |
| 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 |
|
| SmartBear - Zephyr Scale - Test Management for Jira | Node startup time increased significantly | 4.0.5 | 4.0.6 | 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. |
| 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: |
| Structure | Broken Jira screens with Azure CDN | 6.6.0 | 7.0+ | There are reports of Jira screens breaking when enabling Azure based CDN. Structure's fixed this on release 7.0 |
| Tempo for Jira - Tempo Planner - Resource Planning | 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 | 10.18.6 | Thread Dumps shows multiple threads waiting for a cache: | |
| Traffic lights for jira | Seeing strange symbol over the gadget page. | 4.2.4-JIRA8 | Fixed in 4.2.5 |
|
| Xblend - Xray Test Management for Jira | Unnecessary cache flushes XRAY-8115 | 5.1.2 | 5.1.3 | Cache flushes may cause performance degradation and even outages. |
| Xblend - Xray Test Management for Jira | XRAY-7524 DatabaseClusterLock not being unlocked | 4.2.10 | 4.2.14 | Performance Issues with Bulk Edit. |
| Xblend - Xray Test Management for Jira | 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" |
| Xblend - Xray Test Management for Jira | 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. |
| Xblend - Xray Test Management for Jira | High memory / OOM | 3.5.3 | 3.5.4+ | A bug that causes all issues to be loaded through JQL, causing large memory pressure. |
| XBlend - Xporter | High CPU Utilization | v6.7.5 | v6.8.3 and later | Bug: https://jira.getxray.app/browse/XPORTER-3873 |
| Tempo for Jira - Tempo Timesheets - Time Tracking & Reports | Jira menu at the top of the screen disappears when an attachment is viewed | v16.x after upgrade Jira to v9 | v16.3.0 and later | |
| Smart Attachments for Jira | Editing issues from specific projects are not saved correctly. In-line updates still work just fine. | 2.14.11 | 2.14.12 and later. 2.14.10 or earlier. | |
| Rich Filters for Jira Dashboards | Prevents the Webhook administration page from displaying. "Create Webhook" button won't work. | 1.29.0 | 1.29.1 and later | |
| Xray Test Management for Jira | User Mentions feature does not work in Issue Details View under Jira Software Boards | 7.3.0 | 7.4.0 and later | |
| Issue Lock for Jira | Users cannot favourite dashboards | 4.4.10 | ||
| STAGIL Assets | Versions filter and "Add" button missing on "Releases" page | 5.0.109 and 5.0.113 | 6.0.1 |
|
| Gerrit Code Review for Jira | Jira gets stuck | v3.4 | A lot of threads are stuck with SSH connection and making calls to Gerrit: | |
| The Scheduler | The side bar loads very slow in case multiple tickets are opened in a different tab | 6.6.9 |
: Problem is partially fixed, or the Jira Admin should be aware of the potential consequences of the app's functioning.
| Vendor - Plugin | Problem | Affected Version | Update to | Notes | |
|---|---|---|---|---|---|
| Ease Solutions Pte Ltd - R4J - Requirements Management for Jira | High memory usage/OOM | All | None | The Excel plugin that can schedule Excel exports can bring the instance down due to high memory consumption. This can happen if the used JQL covers hundreds thousands of issues. |
| 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. See related KB on Jira becomes unresponsive occasionally and logs several Full GC events. | |
| BigBrassBand - Git Integration for Jira | High disk space consumption. | All versions | High disk space usage on both jira_home/caches/indexes and jira_home/data. Contact support@bigbrassband.com for advice on reducing the number of connected repositories. 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. | |
| Broken Builds - 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. |
| Coverage Services by Ease Solution | High memory consumption | 1.1.3-jira8 | Node | It will no longer cause crashes or instability to a Jira instance as long as the the minimum free memory is configured > 0%. It is also 30% by default. Ref: Configuration - R4J Data Center. |
| Enhancer plugin | High 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 | ||
| iDalko - Exalate Jira Issue Sync & more | 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. | ||
| Enterprise Mail Handler for JIRA(JEMH) | Disables the mail handler system plugin | 4.1.30-dc | 4.1.27-dc | When "Email this issue" and "Enterprise Mail Handler for Jira (JEMH)" plugins are both enabled, and the native Jira Mail plugin is also enabled, then the following is logged when Jira is restarted:
Now, we confirmed that this issue only occurs in the latest 4.1.30-DC version of the Enterprise Mail Handler for JIRA(JEMH) plugin. We see that this got released on Dec 11th 2023, but this seems to be causing some dependency issues. Solution/Workaround : In our testing, we determined that the solution was to uninstall "Enterprise Mail Handler for Jira (JEMH) (version: 4.1.30-DC)" and re-install "Enterprise Mail Handler for Jira (JEMH) (version: 4.1.27-DC), then restart Jira. |
| Xblend - 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 |
| Xblend - Xporter | Unable to enable Xray due to duplicate key | 7.0.0 | None | The duplicate key error (which affects other Jira functionality) can be fixed by following the steps here Duplicate key error. However, the root cause of why the Xray add-on creates duplicated rows in the database is still unknown.
|
: Issue persists. No known fix yet.
| Vendor - Plugin | Problem | Affected Version | Update to | Notes | |
|---|---|---|---|---|---|
| Adaptavist - ScriptRunner | Broken re-indexing SR fields | 5.x | 6.x | Jira re-indexing fails on multiple issues with |
| 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 |
| Adaptavist - ScriptRunner for Jira | OOM Error | All | N/A | Jira fails with Compressed class space error. The workaround is to increase -XX:CompressedClassSpaceSize value (by default, it's 1GB): java.lang.OutOfMemoryError: Compressed class space at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:757) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at groovy.lang.GroovyClassLoader.access$500(GroovyClassLoader.java:89) at groovy.lang.GroovyClassLoader$ClassCollector.createClass(GroovyClassLoader.java:603) at groovy.lang.GroovyClassLoader$ClassCollector.onClassNode(GroovyClassLoader.java:620) at groovy.lang.GroovyClassLoader$ClassCollector.call(GroovyClassLoader.java:624) at org.codehaus.groovy.control.CompilationUnit$18.call(CompilationUnit.java:863) at org.codehaus.groovy.control.CompilationUnit$18.call(CompilationUnit.java:871) at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1084) at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:640) at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:618) at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:595) at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:401) at groovy.lang.GroovyClassLoader.access$300(GroovyClassLoader.java:89) at groovy.lang.GroovyClassLoader$5.provide(GroovyClassLoader.java:341) at groovy.lang.GroovyClassLoader$5.provide(GroovyClassLoader.java:338) at org.codehaus.groovy.runtime.memoize.ConcurrentCommonCache.getAndPut(ConcurrentCommonCache.java:147) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:336) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:320) at groovy.lang.GroovyClassLoader.recompile(GroovyClassLoader.java:858) at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:814) at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:883) at java.lang.ClassLoader.loadClass(ClassLoader.java:406) at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:773) at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:648) at org.codehaus.groovy.control.ClassNodeResolver.findByClassLoading(ClassNodeResolver.java:209) at org.codehaus.groovy.control.ClassNodeResolver.tryAsLoaderClassOrScript(ClassNodeResolver.java:198) at org.codehaus.groovy.control.ClassNodeResolver.findClassNode(ClassNodeResolver.java:169) at org.codehaus.groovy.control.ClassNodeResolver.resolveName(ClassNodeResolver.java:125) at org.codehaus.groovy.control.ResolveVisitor.resolveToOuter(ResolveVisitor.java:853) at org.codehaus.groovy.control.ResolveVisitor.resolve(ResolveVisitor.java:467) ..... ..... |
| Addonrock - Search Linked Issues | OOM Error | 3.1.2-SNAPSHOT-jira8 | N/A | JQL function numberOfLinkedIssuesFromFilter() causes OOM error. |
| ALM Works - Structure | OOM | v8.0.1 | N/A |
|
| Appdynamics | OOM Error/Full GCs | All | N/A | Causing Out-of-memory error because of many instances of: It appears to be related to the https://www.appdynamics.com/product/application-performance-management portion of the product as users of other software have noted similar problems: |
| Appfire - Power Scripts | Moved Issues no longer redirect from previous Issue key or URL in Jira (KB) | 5.8.0.8 and lower | This might've worked in previous versions of the app. | |
| 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. | ||
| Color Cards for Jira | OOM error, making Jira inaccessible | All | For more information about this issue, you can refer to the KB article linked below: | |
| CPrime - 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. |
| All threads are blocked by a single thread and Jira becomes unavailable. | 6.9.0 | N/A | A single thread that has getInputOptions becomes stuck at the database operations: "https-openssl-nio-443-exec-324" #6660058 daemon prio=5 os_prio=0 tid=0x0000000102bc4000 nid=0x1d98 runnable [0x000000012af28000] java.lang.Thread.State: RUNNABLE at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) at java.net.SocketInputStream.read(SocketInputStream.java:171) at java.net.SocketInputStream.read(SocketInputStream.java:141) at com.microsoft.sqlserver.jdbc.TDSChannel.read(IOBuffer.java:2023) at com.microsoft.sqlserver.jdbc.TDSReader.readPacket(IOBuffer.java:6418) - locked <0x00000005a9801d10> (a com.microsoft.sqlserver.jdbc.TDSReader) at com.microsoft.sqlserver.jdbc.TDSCommand.startResponse(IOBuffer.java:7579) at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(SQLServerStatement.java:866) ... | |
| Extension for Jira Service Management | Unable to share customer requests using the Customer portal, even though customer permission is set to Anyone can share. Agents can't share requests either. | 6.12.0 | Following stack trace can be found: | |
| Gerrit Code Review for Jira | Issue 1 - Cannot load issue view | All | None | as noted on https://github.com/MeetMe/jira-gerrit-plugin/issues/84: |
| Issue 2 - High number of stuck HTTP threads in the Jira application, making Jira unavailable | 3.4 | None | Issue reported in https://github.com/MeetMe/jira-gerrit-plugin/issues/96: HTTP threads are stuck in the TIMED_WAITING state with the stack trace below: | ||
| Great Gadgets for Jira Server - by StonikByte | Nodes run into memory pressure:
| 1.37.0 | HeapdumpbeforefullGC reveals leak suspects:
| |
| 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 | 2.0.2_J8 |
| |
| Inversion Point LLC - Raley Email Notifications for Jira / JSM | Updated field is not updated when adding a comment to an issue | All | None | When this plugin is installed, adding comments to issues will not update the "Updated" field. Regardless if you choose "Share with customer" and "Comment internally" when adding a comment, the updated field is not set. |
| Invision for Jira | 5.0.1 | Downgrading to 4.0.5 resolved the issue | Invisionapp caused pop-up screens to become smaller. | |
| Issue Matrix | Export to CSV of Issue Matrix field does not work correctly | All | None | Exporting a JQL to CSV does not work correctly if the JQL contains custom fields from Issue Matrix plugin. The comma separated values are not included in the CSV file, which causes misformatting when loading this data into Excel, for example. |
| StackOverflowError | All | None | StackOverflowError caused by JQL LinkedIssueInFilter. Correspond threads are killed by JVM leaving application in corrupted state. | |
| SaasJet - Time Between Statuses | Unbounded thread creation leading to Too many open files error | All | None | Time Between Statuses has an integrated slack client that uses the library https://github.com/HubSpot/slack-client. at com.hubspot.slack.client.SlackClientFactory$DefaultSlackClientFactory.build(SlackClientFactory.java:28) |
| SAFe EPIC to Feature Translator for Jira | Unable to update Jira license | All | None | it's not possible to update a Jira license (on Manage Apps page) when this plugin is installed and enabled. No error messages are displayed. The progress bar just keeps moving back and forth like Jira is working on the change, but the process never completes. The workaround is to temporarily disable this plugin to apply the license. |
| SmartBear - Zephyr Scale - Test Management for Jira | Please avoid any searches of the format "project = <project name> AND issue not in testsWithoutExecution()" in your searches. | 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). |
| Table Grid Next Generation | 'Too many open files' error: Jira server: IO exception "Too many open files" then crashes | 1.13.3-jira8 1.13.4-jira89 | Downgrade to 1.13.2-jira8 while a fixed version is not available | Command lsof shows multiple files ‘pipe’ and ‘eventpoll’ created: |
| Time To SLA | OOM Error | 10.6.0 | N/A | Caesium thread that runs the TimeToSLA plugin crashes Jira due to OOM problem:
|
| Timesheet Reports and Gadgets | High Memory utilization / Back to back Full GCs | 3.3.13 | Review heap dump | |
| vLinks - easy issue linking | OOM | 2.2.4-jira8-2021-11-12-09-18 | OOM error when compareJqlSearchesFunction function is used via /rest/issueNav/1/issueTable call. | |
| Xblend - Xray Test Management for Jira | OOM Error/Full GCs | v6.1.0 | N/A | /rest/raven/1.0/report/testrunsreport/testruns/ requests allocate a lot of memory and causes OOM error. at java.nio.HeapByteBuffer.<init>(II)V (HeapByteBuffer.java:57) |
| Zephyr Squad - Test Management for Jira | Advanced Roadmaps plans fails to load | All | None | Advanced Roadmaps plans fails to load with the following error: Atlassian Support has received reports of this error message after Zephyr plugin is installed. Either uninstall or disable Zephyr as a workaround for this issue and engage with SmartBear for further information. |
| Optimizer for Jira | OOM Error | 4.3.3 | Not known yet | OOM error while executing a scheduled task and retrieving a result set from the database. If the result set is large, it causes an OOM error: This is what is seen in the heap dump: |
| BigPicture - Project Management & PPM | Date fields being updated by Date Synchronization without informing users of the source of it. | All | None | Users may report Date fields are getting changed unexpectedly or getting changed back immediately after they update them. BigPicture has a Date Synchronization feature which will update issues using the users account. A ticket was created for AppFire suggesting a way to identify these changes: https://appfire.atlassian.net/servicedesk/customer/portal/42/SUPPORTBP-388776 |
