-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
4
-
8
-
NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.
JIRA Service Desk: 3.3.0
Problem when allocating existing customer to organization.
All our users are already defined in JSD via AD sync. When we allocate users to organization in JSD, an invitation is sent to the staff. Following the link asks them to sign up to the service desk. (They are existing users, and causes significant confusion).
(Tried to search for existing open tickets on this but havent found any. Please close ticket if this issue is already logged)
- is related to
-
- Gathering Interest
- relates to
-
- Gathering Interest
- links to
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDSERVER-4641] Disable invitation email when assigning customer to organization
@daphne.thunnissen When we add a user that already exists in that project to an organization a verification email does NOT send, I just tested it again to be sure. Since we turned that "Account verification email" setting on in the SD project emails are no longer going out (thankfully). We have an LDAP user directory so all of our users are created automatically when it synchronizes, so we would never be adding a brand new user to an organization we do it as sort of a cleanup after the fact. Not sure if our user directories are playing a part or if it's a versioning difference between our environments (we have JIRA Service Desk version 4.5.4 for server) but this setting does work as expected for us.
@Brainna Pasko; that's not the solution. If a customer already exists in the project and you add them to an Organization an email is sent. So disabling the "Do not send account verification emails" doesn't help as the person already exists.
This is actually now an option in Service Desk 4.5 (specifically we have 4.5.4). 
Under Customer Notifications there's now an option to disable them. "Do not send account verification emails"
This is not a functional workaround, because in the meantime there will no e-mails be send at all. This could be even worse than getting an invitation e-mail.
This will not work when the users are auto-created or you have automated email traffic.
Workaround:
- Disable Outgoing Mail from Administration -> System -> Outgoing Mail.
- Add users to organization.
- Enable Outgoing Mail.
We worked around the problem by using the REST API to add users to organization. This bypasses sending the e-mail to the users.
Information is here.
This is how we worked around the problem.
- setup a local fake SMTP server (we used Dumbster: https://github.com/kirviq/dumbster)
- enable debugging on the Jira Outgoing Mail debug log
- configure the Jira Outgoing Mail Server to point to the fake SMTP server
- create the Organization and paste the list of users into it
- configure the Jira Outgoing Mail Server to point back to it's original host
- disable debugging on Outgoing Mail debug log
- check the Outgoing Mail log for any valid emails that might have been sent to the fake SMTP server
@Brainna Pasko: you are absolutely right. I tested it today and no mails were sent. So guess I did something other then I thought I did when a mail was sent. Thank you so much for the help. (Jira Service Management 4.14.1)