Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-14817

Add flag and comment is not working on Service Desk projects

XMLWordPrintable

      NOTE: This bug report is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding bug report.

      Summary

      If you select the button Add flag and comment (board view), it will open a new screen to add a comment, if you select add nothing will happen and you won't be able to cancel the operation, the screen will freeze.
      It happens only when the issue on that board is associated to a Service Desk Project.

      Steps to Reproduce

      1. Create a board that contains issues from a JIRA Service Desk project.
      2. Click either Backlog, Active sprints, or Kanban board.
      3. Select an issue from a JSD project within the board
      4. Click the issue then in question and in the Issue Detail View, select "Add flag and comment".
      5. Write the comment and try to add it.

      Expected Results

      The issue will be flagged and a comment added to the issue.

      Actual Results

      The screen freezes in JIRA Cloud instances.
      In JIRA Server an error is thrown on the screen of

      Exception: Uncaught TypeError: Cannot read property 'trim' of undefined

      Workaround

      Add the flag and the comment separately (not applicable for Cloud).

        1. typeerror1.png
          typeerror1.png
          548 kB

            [JSWSERVER-14817] Add flag and comment is not working on Service Desk projects

            Bianca van der Meer added a comment - - edited

            Error occurs as well on Data Center 
            Jira Service Management 5.12.8

            Issue also occurs when removing flag and comment from a Service Management Issue.

            Bianca van der Meer added a comment - - edited Error occurs as well on Data Center  Jira Service Management 5.12.8 Issue also occurs when removing flag and comment from a Service Management Issue.

            Edgar Koenig - SVA added a comment -

            The error occurs as well on

            • Jira 9.12.7 and
            • Jira Service Desk 5.12.7

            Edgar Koenig - SVA added a comment - The error occurs as well on Jira 9.12.7 and Jira Service Desk 5.12.7

            MiskaT added a comment -

            Also affected in version 9.12.5

            MiskaT added a comment - Also affected in version 9.12.5

            Christopher Orendi added a comment -

            Jira DC 9.4.12 is also affected.

            Christopher Orendi added a comment - Jira DC 9.4.12 is also affected.

            Manuel Herrmann added a comment -

            Hi, we are getting the same error with Version 8.20.11, both tested with

            Firefox: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/119.0
            Google Chrome: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36

            Manuel Herrmann added a comment - Hi, we are getting the same error with Version 8.20.11, both tested with Firefox: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/119.0 Google Chrome: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36

            Bojana Vasic added a comment -

            Issue exists in JSD server 4.20.11. Please ETA for the fix

            Bojana Vasic added a comment - Issue exists in JSD server 4.20.11. Please ETA for the fix

            Robertas Reiciunas added a comment -

            Same with Jira Data Center 9.4.0, 9.50 and JSM 5.4.0 and 5.5.0

            Robertas Reiciunas added a comment - Same with Jira Data Center 9.4.0, 9.50 and JSM 5.4.0 and 5.5.0

            Štefan Tóth added a comment -

            Same with JIRA 9.2.0 and JSM 5.2.0

            Å tefan Tóth added a comment - Same with JIRA 9.2.0 and JSM 5.2.0

            danna deaton added a comment -

            Occurs with Jira Service Management 4.20.1 and 

            Jira Software 8.20.1

            danna deaton added a comment - Occurs with Jira Service Management 4.20.1 and  Jira Software 8.20.1

            Eric Roblin added a comment -

            I see that this bug was fixed on Cloud version in 2017.

            Is it fixed on Server version now ?? In which version ?

            Eric Roblin added a comment - I see that this bug was fixed on Cloud version in 2017. Is it fixed on Server version now ?? In which version ?

              npellow Nick
              aschneider@atlassian.com Adalberto Schneider
              Affected customers:
              91 This affects my team
              Watchers:
              84 Start watching this issue

                Created:
                Updated: