Commenting on a selected ticket within the backlog using comment button shows an error bar
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. 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
Problem
When commenting on a selected ticket within the backlog (using the comment button within the selected ticket on the right hand side of the view) you will get a red error bar
Diagnosis
Errors similar to the following ones are shown
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
Exception: Uncaught Error: "Add comment" form could not be found
Resource: https://jira.sarc.samsung.com/s/b4800c7c8e37f8c071179dde27f0c561-T/1rhvzl/940003/zc8yjd/df1e3c1165e9fd015e6ab81b30af0792/_/download/contextbatch/js/com.atlassian.jira.jira-frontend-plugin:64,-_super,-gh-rapid-detailsview,-jira.rich.editor.api,-com.atlassian.jira.plugins.jira-development-integration-plugin:0,-atl.general,-jira.rich.editor,-gh-rapid-plan/batch.js?agile_global_admin_condition=true&baseurl-check-resources=true&extensiIoAbf=true&flexboards=true&healthcheck-resources=true&jag=true&jaguser=true&locale=en-US&richediton=true
Line: 5
Column: 35479
Environment
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36 Edg/110.0.1587.69
Stack trace
Error: "Add comment" form could not be found
at i (https://jira.sarc.samsung.com/s/b4800c7c8e37f8c071179dde27f0c561-T/1rhvzl/940003/zc8yjd/df1e3c1165e9fd015e6ab81b30af0792/_/download/contextbatch/js/com.atlassian.jira.jira-frontend-plugin:64,-_super,-gh-rapid-detailsview,-jira.rich.editor.api,-com.atlassian.jira.plugins.jira-development-integration-plugin:0,-atl.general,-jira.rich.editor,-gh-rapid-plan/batch.js?agile_global_admin_condition=true&baseurl-check-resources=true&extensiIoAbf=true&flexboards=true&healthcheck-resources=true&jag=true&jaguser=true&locale=en-US&richediton=true:5:35485\)
at CommentForm.value (https://jira.sarc.samsung.com/s/b4800c7c8e37f8c071179dde27f0c561-T/1rhvzl/940003/zc8yjd/df1e3c1165e9fd015e6ab81b30af0792/_/download/contextbatch/js/com.atlassian.jira.jira-frontend-plugin:64,-_super,-gh-rapid-detailsview,-jira.rich.editor.api,-com.atlassian.jira.plugins.jira-development-integration-plugin:0,-atl.general,-jira.rich.editor,-gh-rapid-plan/batch.js?agile_global_admin_condition=true&baseurl-check-resources=true&extensiIoAbf=true&flexboards=true&healthcheck-resources=true&jag=true&jaguser=true&locale=en-US&richediton=true:5:33850\)
at CommentForm.value (https://jira.sarc.samsung.com/s/b4800c7c8e37f8c071179dde27f0c561-T/1rhvzl/940003/zc8yjd/df1e3c1165e9fd015e6ab81b30af0792/_/download/contextbatch/js/com.atlassian.jira.jira-frontend-plugin:64,-_super,-gh-rapid-detailsview,-jira.rich.editor.api,-com.atlassian.jira.plugins.jira-development-integration-plugin:0,-atl.general,-jira.rich.editor,-gh-rapid-plan/batch.js?agile_global_admin_condition=true&baseurl-check-resources=true&extensiIoAbf=true&flexboards=true&healthcheck-resources=true&jag=true&jaguser=true&locale=en-US&richediton=true:5:31609\)
at CommentForm.value (https://jira.sarc.samsung.com/s/b4800c7c8e37f8c071179dde27f0c561-T/1rhvzl/940003/zc8yjd/df1e3c1165e9fd015e6ab81b30af0792/_/download/contextbatch/js/com.atlassian.jira.jira-frontend-plugin:64,-_super,-gh-rapid-detailsview,-jira.rich.editor.api,-com.atlassian.jira.plugins.jira-development-integration-plugin:0,-atl.general,-jira.rich.editor,-gh-rapid-plan/batch.js?agile_global_admin_condition=true&baseurl-check-resources=true&extensiIoAbf=true&flexboards=true&healthcheck-resources=true&jag=true&jaguser=true&locale=en-US&richediton=true:5:30565\)
at CommentForm.value (https://jira.sarc.samsung.com/s/b4800c7c8e37f8c071179dde27f0c561-T/1rhvzl/940003/zc8yjd/df1e3c1165e9fd015e6ab81b30af0792/_/download/contextbatch/js/com.atlassian.jira.jira-frontend-plugin:64,-_super,-gh-rapid-detailsview,-jira.rich.editor.api,-com.atlassian.jira.plugins.jira-development-integration-plugin:0,-atl.general,-jira.rich.editor,-gh-rapid-plan/batch.js?agile_global_admin_condition=true&baseurl-check-resources=true&extensiIoAbf=true&flexboards=true&healthcheck-resources=true&jag=true&jaguser=true&locale=en-US&richediton=true:5:32490\)
at HTMLDivElement.dispatch (https://jira.sarc.samsung.com/s/7f4f408cf079aeca5de8d4eb40e58ba1-CDN/1rhvzl/940003/zc8yjd/cae9f2d6eb733204c34664d84b5456d4/_/download/contextbatch/js/_super,-com.atlassian.plugins.atlassian-plugins-webresource-rest:data-collector-perf-observer,-jira.webresources:resource-phase-checkpoint-init/batch.js?locale=en-US:154:3915\)
at v.handle (https://jira.sarc.samsung.com/s/7f4f408cf079aeca5de8d4eb40e58ba1-CDN/1rhvzl/940003/zc8yjd/cae9f2d6eb733204c34664d84b5456d4/_/download/contextbatch/js/_super,-com.atlassian.plugins.atlassian-plugins-webresource-rest:data-collector-perf-observer,-jira.webresources:resource-phase-checkpoint-init/batch.js?locale=en-US:154:2004\)
at a.__trace__ (https://jira.sarc.samsung.com/s/3b90bf7564f1ceac0611d45f7a07de61-T/1rhvzl/940003/zc8yjd/e510fa14031725b74dca9f87809ff0de/_/download/contextbatch/js/gh-rapid-plan,atl.general,gh-rapid-detailsview,greenhopper-rapid-non-gadget,jira.general,jira.global,com.atlassian.jira.jira-projects-plugin:sidebar-placeholder,-_super/batch.js?agile_global_admin_condition=true&baseurl-check-resources=true&extensiIoAbf=true&flexboards=true&healthcheck-resources=true&jag=true&jaguser=true&locale=en-US&richediton=true:108854:357506\)
Cause
This issue is happens when a JavaScript exception happens in an UI component.
The most likely cause is that a 3rd party app is causing the issue.
Solution
The trick is to find which 3rd party add-on(s) are causing this issue. One way to figure it out is to:
enable plugin safe mode
check if the issue goes away
if the issue goes away, then re-enable each 3rd party add-on 1 by 1, until the issue occurs again, then the last add-on you enabled is the culprit
Some admins found that one of the the following add-ons was the culprit and needed to be disabled (or un-installed, if disabling it was not enough to fix the problem):
Was this helpful?