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

Creating a Service Desk request using the *Raise this request on behalf of* parameter causes the user who creates the request to be added as a watcher

XMLWordPrintable

      Summary

      Creating a Service Desk request using the Raise this request on behalf of parameter causes the user who creates the request to be added as a watcher.

      Steps to Reproduce

      1. Log into Service Desk as a user that is a Service Desk Agent
      2. Create a request using Raise a request from the project settings sidebar.

      Expected Results

      The request is created for the customer with no watchers added to the issue.

      Actual Results

      The request is created but adds the user who created the request on behalf of the user.

      Notes

      This behavior was tested on Service Desk 3.10.1 and 4.4.2. This behavior does not occur on 3.10.1 but does occur on 4.4.2. The issue can also be reproduced via the API creating a request to Base-URL/rest/servicedeskapi/request/ using a body like so:

      {
"serviceDeskId": "1",
"requestTypeId": "1",
"requestFieldValues": {
"summary": "test ticket summary",
"description": "test ticket creation"
},
"raiseOnBehalfOf": "jeremy"
}

      Creating an issue using the Raise a request button inside of the Service Desk project also exhibits the same behavior on 4.4.2 but not on 3.10.1.

      Workaround

      Have the customer create their request via the portal.

          Form Name

            [JSDSERVER-6604] Creating a Service Desk request using the *Raise this request on behalf of* parameter causes the user who creates the request to be added as a watcher

              Unassigned Unassigned
              jsanchez2@atlassian.com Jeremy Sanchez
              Affected customers:
              1 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: