Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-4379

Unable to edit comments when attachments are disabled

    XMLWordPrintable

Details

    Description

      Summary

      It is not possible to edit a JIRA Service Desk comment when attachments are disabled in the JIRA Core settings.

      Environment

      • JIRA Core 7.2.x
      • JIRA Service Desk 3.2.x

      Steps to Reproduce

      1. Disable file attachments - Configuring file attachments.
      2. Add a comment to a Service Desk enabled project.
      3. Try to edit the comment.
      4. Click on either 'Share with customer' or 'Add to issue only'.

      Expected Results

      Editing the comment works and the comment is saved.

      Actual Results

      A red banner is displayed with the error:

      Failed to attach files

      You do not have permission to create attachments for this issue.

      The warning below is written to the standard Tomcat log (e.g. catalina.out) file:

      11-Oct-2016 16:57:18.155 WARNING [http-nio-8721-exec-17] com.sun.jersey.spi.container.servlet.WebComponent.filterFormParameters A servlet request, to the URI http://jira.baseurl/rest/jddap/1.0/attachment, contains form parameters in the request body but the request body has been consumed by the servlet or a servlet filter accessing the request parameters. Only resource methods using @FormParam will work as expected. Resource methods consuming the request body by other means will not work as expected.
      

      Notes

      Creating and deleting comments work as expected.

      Workaround

      Enable file attachments before editing the comments.

      Attachments

        Issue Links

          Activity

            People

              agoldthorpe Aidan Goldthorpe
              dconrad Danilo Conrad
              Votes:
              4 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Backbone Issue Sync