-
Suggestion
-
Resolution: Won't Do
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
With the current mail handler, if Jira receives an email whose address is associated with a user that does not have permission to comment or create issues, the email is rejected. However, if the address is not associated with any user, and the handler has a reporterusername, then the comment will be added as that default user.
This ends in the absurd situation where a non existing user can add comments to a case, but an existing user cannot. This user could then create a bogus email account to add comments to the issue.
In my understanding, the logic of the handleMessage/getReporter mail handlers should be changed. For the previous case (existing user but no permissions) the logic should be:
- Get user from email
- If user exists, check if user has permission to perform operation
- If no permissions, fall back to reporterusername
I am aware that JRA-16786 was raised in the past with a similar request, and the functionality was claimed to be like that by design. However, I think the situation I describe is a flaw in that design.
If the logic was as described before, we could have avoided creating the proxy commenter for SAC to fix JRA-15431. The proxy commenter performs the logic as described before (with some additional magic)
- is related to
-
JRACLOUD-26446 CreateOrCommentHandler needs improved handling for LDAP users that have not yet logged in
- Closed
-
JRASERVER-19874 CreateOrCommentHandler should fall back to defaultreporter if email user does not have permissions to perform operation
- Closed