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

In portal attempt to share with reporter throws "failed to update request participants field, error"

XMLWordPrintable

      Issue Summary

      If a user A creates an issue and a user B is added as the participant, if user B inherits the issue and is made the reporter but not removed from the request participant field, all attempts to share the issue in question with other users from the customer portal will throw the error seen below:

      Steps To Reproduce
      1. Create an issue as User A in a JIRA Service Desk project.
      2. Add a user B to the issue as a request participant.
      3. Modify the reporter field from inside JIRA (as an Agent) setting user B as the reporter.
      4. As a user go to customer portal and attempt to share the issue with any other user(other than user B)
      Expected Behavior

      JIRA would share the issue with the other user entered.

      Actual Behavior

      JIRA would throw the error thrown in the image above and if you look at the Network tab in the developer console, it would throw an HTTP 500 response.

      Workaround

      Remove the user B from the request participant field. Also, if you attempt to add the user from within the JIRA UI, it would alert you correctly that the reporter cannot be in the participant field.

        1. screenshot-1.png
          52 kB
          Ismael Olusula Jimoh
        2. screenshot-2.png
          13 kB
          Ismael Olusula Jimoh

          Form Name

            [JSDSERVER-5112] In portal attempt to share with reporter throws "failed to update request participants field, error"

            set-jac-bot made changes -
            Fixed in Enterprise Release/s New: [Download 3.9|https://confluence.atlassian.com/enterprise/atlassian-enterprise-releases-948227420.html]
            Owen made changes -
            Workflow Original: JSD Bug Workflow v5 - TEMP [ 2304049 ] New: JAC Bug Workflow v3 [ 3126166 ]
            Status Original: Done [ 10044 ] New: Closed [ 6 ]
            Owen made changes -
            Symptom Severity Original: Major [ 14431 ] New: Severity 2 - Major [ 15831 ]
            Milap Wadhwa (Inactive) made changes -
            Fix Version/s New: 3.9.7 [ 80090 ]
            Fix Version/s New: 3.13.1 [ 80091 ]
            Fix Version/s New: 3.14.0 [ 80092 ]
            Resolution New: Fixed [ 1 ]
            Status Original: In Progress [ 3 ] New: Done [ 10044 ]
            Milap Wadhwa (Inactive) made changes -
            Link New: This issue is related to JSDSERVER-5162 [ JSDSERVER-5162 ]
            Milap Wadhwa (Inactive) made changes -
            Status Original: To Do [ 10071 ] New: In Progress [ 3 ]

            Milap Wadhwa (Inactive) added a comment -

            Hi,

             

            This was fixed part of https://jira.atlassian.com/browse/JSDSERVER-5162 in release versions : 3.9.7, 3.14.0, 3.13.1 .

             

            –

            Jira Service Desk Team

            Milap Wadhwa (Inactive) added a comment - Hi,   This was fixed part of  https://jira.atlassian.com/browse/JSDSERVER-5162  in release versions :  3.9.7, 3.14.0, 3.13.1 .   – Jira Service Desk Team
            Milap Wadhwa (Inactive) made changes -
            Assignee New: Milap Wadhwa [ mwadhwa@atlassian.com ]
            Lachlan G (Inactive) made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 378821 ]
            SET Analytics Bot made changes -
            Support reference count New: 3

              mwadhwa@atlassian.com Milap Wadhwa (Inactive)
              ijimoh Ismael Olusula Jimoh (Inactive)
              Affected customers:
              2 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: