• Type: Bug
• Resolution: Obsolete
• Priority: Low
• Fix Version/s: 3.9.7, 3.13.1, 3.14.0
• Affects Version/s: 3.5.0
• Component/s: Issue View
• Labels:

  None

1. 

   screenshot-2.png

   13 kB

   09/Jun/2017 7:14 PM

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

set-jac-bot made changes - 22/May/2020 8:10 AM

Fixed in Enterprise Release/s

New: [Download 3.9|https://confluence.atlassian.com/enterprise/atlassian-enterprise-releases-948227420.html]

Collapse comment: Jacek Choroszewicz added a comment - 11/Sep/2019 3:18 PM

Jacek Choroszewicz added a comment - 11/Sep/2019 3:18 PM

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.

Expand comment: Jacek Choroszewicz added a comment - 11/Sep/2019 3:18 PM

Jacek Choroszewicz added a comment - 11/Sep/2019 3:18 PM 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.

Owen made changes - 27/Mar/2019 5:47 AM

Workflow	Original: JSD Bug Workflow v5 - TEMP [ 2307689 ]	New: JAC Bug Workflow v3 [ 3126359 ]
Status	Original: Done [ 10044 ]	New: Closed [ 6 ]

Owen made changes - 24/Oct/2018 5:23 AM

Symptom Severity

Original: Minor [ 14432 ]

New: Severity 3 - Minor [ 15832 ]

Lachlan G (Inactive) made changes - 30/May/2018 12:59 AM

Assignee

New: Lachlan G [ lgoodhewcook ]

Lachlan G (Inactive) made changes - 30/May/2018 12:59 AM

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: Obsolete [ 11 ]
Status	Original: Untriaged [ 11672 ]	New: Done [ 10044 ]

Collapse comment: Lachlan G (Inactive) added a comment - 30/May/2018 12:59 AM

Lachlan G (Inactive) added a comment - 30/May/2018 12:59 AM

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

Expand comment: Lachlan G (Inactive) added a comment - 30/May/2018 12:59 AM

Lachlan G (Inactive) added a comment - 30/May/2018 12:59 AM 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

Michelle Chin made changes - 08/Sep/2017 1:15 PM

Link

New: This issue is related to JSDSERVER-5162 [ JSDSERVER-5162 ]

Russell Stadler (Inactive) made changes - 09/Jun/2017 7:15 PM

Attachment		New: screenshot-2.png [ 283594 ]
Description		New: h3. 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. h3. Steps to Reproduce  # Raise a request from customer1  # Add customer2 as a request participant  # Change the Reporter to customer2 h3. 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. !screenshot-2.png! Image copied from JSDSERVER-5112 h3. 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) h3. Workaround Manually update the field(s) to avoid having the same user as both Reporter and Participant.

Russell Stadler (Inactive) created issue - 09/Jun/2017 7:12 PM