Editing a JSM issue comment twice in a row while using canned responses cause Console error

XMLWordPrintable

    • 2
    • Severity 3 - Minor
    • 7

      Issue Summary

      After a user edits a latest comment, cancels the edit, and then attempts to edit the same comment again and insert a canned response, the canned response is not inserted and a console error appears. The issue persists until the browser page is refreshed.

      Steps to Reproduce

      1. Create a JSM Project.
      2. Create one or more issues in the project with at least one comment.
      3. Create a canned response:
        • Click Edit responses → Add a response, then save it.
      4. Open an issue with comments.
      5. Refresh the issue page.
      6. Edit the last comment:
        • Modify the text.
        • Insert a canned response.
        • Click Cancel to discard changes.
      7. Edit the same (last) comment again.
        • Attempt to insert the same or any canned response.

      Loom video link (10.3.12):

      Demo - Canned Response

      Expected Results

      Canned response should be inserted.

      Actual Results

      Console error is observed:

      Uncaught TypeError: Cannot read properties of null (reading 'contentDocument')
    at Object._setTextAreaHeight (batch.js?agile_global_admin_condition=true&analytics-enabled=false&assets-chaperone-condition-assets-imports-global-view-chaperone-sync-key=true&chaperone-condition-share-request-with-groups-issue-view-chaperone=true&condition-share-request-with-groups=true&feature-flag-condition-assets.imports.global.view=true&feature-flag-condition-assets.imports.global.view.chaperone=true&jag=true&jaguser=true&jira.create.linked.issue=true&locale=en-UK&plugins.jquery.migrate.not.load=false&richediton=true&slack-enabled=true&user-logged-in=true:630:17)
    at Object._preview (batch.js?agile_global_admin_condition=true&analytics-enabled=false&assets-chaperone-condition-assets-imports-global-view-chaperone-sync-key=true&chaperone-condition-share-request-with-groups-issue-view-chaperone=true&condition-share-request-with-groups=true&feature-flag-condition-assets.imports.global.view=true&feature-flag-condition-assets.imports.global.view.chaperone=true&jag=true&jaguser=true&jira.create.linked.issue=true&locale=en-UK&plugins.jquery.migrate.not.load=false&richediton=true&slack-enabled=true&user-logged-in=true:630:214)
    at C (batch.js?_v=357c344&agile_global_admin_condition=true&analytics-enabled=false&assets-chaperone-condition-assets-imports-global-view-chaperone-sync-key=true&chaperone-condition-share-request-with-groups-issue-view-chaperone=true&condition-share-request-with-groups=true&feature-flag-condition-assets.imports.global.view=true&feature-flag-condition-assets.imports.global.view.chaperone=true&jag=true&jaguser=true&jira.create.linked.issue=true&locale=en-UK&plugins.jquery.migrate.not.load=false&richediton=true&slack-enabled=true&user-logged-in=true:2251:131)
    at Object.trigger (batch.js?_v=357c344&agile_global_admin_condition=true&analytics-enabled=false&assets-chaperone-condition-assets-imports-global-view-chaperone-sync-key=true&chaperone-condition-share-request-with-groups-issue-view-chaperone=true&condition-share-request-with-groups=true&feature-flag-condition-assets.imports.global.view=true&feature-flag-condition-assets.imports.global.view.chaperone=true&jag=true&jaguser=true&jira.create.linked.issue=true&locale=en-UK&plugins.jquery.migrate.not.load=false&richediton=true&slack-enabled=true&user-logged-in=true:2249:477)

       

      Workaround

      1. Refresh the page before editing a comment

              Assignee:
              Piyush Sonagara
              Reporter:
              Meenakshi Jha
              Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: