• Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Low Low
    • 3.9.7, 3.13.1, 3.14.0
    • 3.5.0
    • Issue View
    • None

      Summary

      While JIRA will stop you from setting the Request Participant field to include the Reporter, it does not appear to enforce the same restriction when setting the Reporter.

      Steps to Reproduce

      1. Raise a request from customer1
      2. Add customer2 as a request participant
      3. Change the Reporter to customer2

      Expected Results

      A warning similar to that given when trying to set the Request Participant to include the Reporter, and the action to be blocked.

      Image copied from JSDSERVER-5112

      Actual Results

      The reporter and request participant are set to the same user, giving rise to other known issues (e.g. Having the same user as reporter and request participants leaves the issue not transitionable through customer portal)

      Workaround

      Manually update the field(s) to avoid having the same user as both Reporter and Participant.

            [JSDSERVER-5168] JIRA does not prevent setting Reporter to a Request Participant

            Well, maybe that solved the problem described in this issue but it seems it created different problems at the same time: https://jira.atlassian.com/browse/JSDSERVER-3504.

            Especially that one can be added as a participant only being on the CC of the original mail that creates the issue.

            Jacek Choroszewicz added a comment - Well, maybe that solved the problem described in this issue but it seems it created different problems at the same time:  https://jira.atlassian.com/browse/JSDSERVER-3504 . Especially that one can be added as a participant only being on the CC of the original mail that creates the issue.

            In the noted fix versions we've removed the restriction that the reporter can't also be a request participant solving the mentioned bugs so this is no longer relevant

            Lachlan G (Inactive) added a comment - In the noted fix versions we've removed the restriction that the reporter can't also be a request participant solving the mentioned bugs so this is no longer relevant

              lgoodhewcook Lachlan G (Inactive)
              rstadler@atlassian.com Russell Stadler (Inactive)
              Affected customers:
              0 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: