Issue Summary

When a Kanban Board is created for a "Jira Service Management Project" and the tickets from the JSM Project contain a "canned response," the following issue is observed:

• The first ticket can be transitioned smoothly on the Board, and the user can select the "canned response" on the transition screen.

• However, when the second ticket is transitioned on the Board, if the user clicks on the "canned response" icon during the transition, a console error is observed.

Steps to Reproduce

1. Create a JSM Project.
2. Create few tickets in JSM project.
3. Create a "canned response" by clicking on "Edit responses"->"Add a response"
   
   
4. Create a "Kanban" Board for the JSM Project created in Step 1
5. Transition one issue for example "SD-9" below by moving issue on the Board and during transition select a "canned response" created in step 3. The transition for "SD-9" gets completed fine.
   
6. Now, transition second issue for ex-"SD-8" by moving issue on the Board and during transition select a "canned response" and Error like below is seen.
   

Note- The transition in Step 6 still completes fine. However, a console error is observed.

Expected Results

When the second ticket is transitioned on the Board, if the user clicks on the "canned response" icon during the transition, a console error should not occur.

Actual Results

When the second ticket is transitioned on the Board, if the user clicks on the "canned response" icon during the transition, a console error like below is seen:

Exception: Uncaught TypeError: Cannot read properties of null (reading 'contentDocument')
Resource: https://localhost:9129/j1033/s/554664929a4a11241ec7b6e5e8f9afcb-CDN/lyv28q/10030003/1bqcfwe/39c6c90a23e6917099291811a32e10f5/_/download/contextbatch/js/jira.webresources:mentions-feature,jira.rich.editor.api,jira.rich.editor,-_super,-gh-rapid-detailsview,-jira.global,-greenhopper-rapid-non-gadget,-gh-rapid-work,-com.pyxis.greenhopper.jira:gh-rapid,-atl.general,-jira.project.sidebar,-com.atlassian.jira.plugins.jira-development-integration-plugin:11,-jira.webresources:calendar-localisation-moment/batch.js?agile_global_admin_condition=true&assets-chaperone-condition-assets-imports-global-view-chaperone-sync-key=true&baseurl-check-resources=true&feature-flag-condition-assets.imports.global.view=true&feature-flag-condition-assets.imports.global.view.chaperone=true&flexboards=true&healthcheck-resources=true&jag=true&jaguser=true&jira.create.linked.issue=true&locale=en-IN&plugins.jquery.migrate.load.disabled=false&richediton=true&whisper-enabled=true
Line: 774
Column: 17 

Workaround

If the console Error is observed, refresh the browser and then try to transition the ticket again.