How Jira define a unique user and identify a unique user

sc October 14, 2019

 

Dear all,

We are using Jira Data-Center and we have issue with unique users in Jira database.

It seems to me that Jira identify unique users by its user_key and lower_user_name, is it really the case ?

2019-10-14_11-40-01.png

Because sounds to be by doing so we have duplicate user account in database for same user

Thanks for clarification

regards

2 answers

0 votes
fran garcia gomera
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 14, 2019

You can define the order of the user directories. I think only the first one would be used in case of a repetition.

Yoou could check if that is happening with a query to cwd_user to get possible duplicates in low_user_name.

sc October 14, 2019

My AD directory is define first in the order list from the UI but that does not means that records in cwd_user are in same order..

What type of querry are you thinking about ?

fran garcia gomera
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 14, 2019

cwd_user has a field called directory_id, i think jira gives precedence to rows ordering by that directory, I would say even in loging into the app.

something like this

SELECT lower_user_name, directory_id, COUNT(lower_user_name) 
FROM cwd_user
GROUP BY lower_user_name
HAVING COUNT(lower_user_name) > 1
0 votes
fran garcia gomera
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 14, 2019

In relations between tables jira uses lower_user_name as id of the user (for instance in worklog table, or as reporter, creator or assignee in jiraissue table or in changeitem via changegroup or even cwd_membership) idon't remember any relation defined using the user id.

sc October 14, 2019

This is wierd if it is using the field lower_user_name , because you could potentially have different lower user name field for a same user internal and external for instance, and if internal is scan first it will take this entry instead of the syn AD.

Anyway to avoid this ?

Suggest an answer

Log in or Sign up to answer