We have Jira configured to use LDAP (AD) as a primary source for user-accounts, "JIRA Internal Directory" as secondary.
In our Service Desk projekt we have configured that everyone can share the issue by entering an Email address ("Any customer, by typing an email address").
Now I have found out that a lot of new users have been created in our JIRA internal directory, even if they (or their email) exist on the AD (using the email address as username in internal directory).
User from AD:
Full Name: Bart Simpson
Email: firstname.lastname@example.org (primary mail from AD)
If anyone adds someone via mail to a SD-Request a new user gets created in JIRA Internal Directory:
Full Name: email@example.com
So we have duplicate user entries for same email address :-(
This sounds strange. I would agree that I don't think Jira should be creating new accounts with the same email address for a user that already exists in jira with the same email address. But perhaps this is a problem with the way Service Desk handles this.
Could you please let me know the following:
I'd like to try to recreate this scenario if I can learn more about your versions and setting here. It sounds like it might be a bug, but I'd like to be sure before we create one here.
thanks for your answer. See below my answers to your questions and some new findings:
It seems that it also has to do with people having signed in before. If I add someone via mail and the one had been logged in before it can match the accounts and does not create an Internal Directory entry.
When I am in the portal:
Hope this helps...
Thanks for detailing all that information here. I tried to recreate this in my own environment. However so far I have been unsuccessful. I'd like to see if I can get a support zip from your environment. With this information, I think I can learn a lot more about your specific environment that might be able to account for this discrepancy here.
Unfortunately, our Community site itself doesn't permit file uploads aside from images. If you could upload this support zip to a service like Dropbox, google drive, or alike, and then share the link here, I'll take a look and see if I can better understand what is causing this.
Hi @Jörg T_
I created a support request on your behalf over in https://getsupport.atlassian.com/servicedesk/customer/portal/3/SDS-41626
Here you can upload your support zip and our support team can look into this more deeply. I suspect that there might be something out of line in regards to the application encoding and/or database collation that Jira might be using here. But that is mostly just a hunch here, I think that some more data about your environment from the support zip can probably give us more insights here.
I found that this support ticket ended up creating this new KB Sharing request by Email Address creates a new account instead of using the Existing ones.
In it they found that there appears to be a workaround where restarting Jira appears to be able to clear a user cache that can help avoid this problem. So I hope that helps, please try that and let me know if this helps or not.
In the meantime, I think that this should probably be documented as a bug in regards to the user cache in Jira. I will look into creating a new bug ticket for this. Could you let me know what version of Jira and Service Desk you are running where you see this problem?
Hello Insight users, As part of our (Mindville's) acquisition by Atlassian, our training team is looking to build some new Insight training materials. It would really helpful if you can ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event