There is a particular user, when a issue gets assign to him the ID is not visible properly.

[Megha Sinha]

Instead of userId 'janic1' its showing JIRAUSER114400.

The user left the organization once and rejoined again,Hence there are two entries in Users.

[Kian Stack Mumo Systems]

@Megha Sinha, this isn't a cause for concern. What you are seeing is the "user-key" of the user. Prior to Jira 8.2, the username always matched the user key, unless the user key was already taken, or the username had been manually changed.

Since Jira 8.2, they've changed user keys to be "anonymized" as you see in the screenshots you've shared.

I wouldn't worry about this. Also, I'd consider taking down some of the screenshots containing personal information such as names and email addresses.

[Megha Sinha]

But, its not for the old username, its happening for the current user, who is active.

Whenever, he is getting any issue assigned his current userkey is not visible.

[Daniel Ebers]

I see what you mean but as Kian already said this is how it was designed to work for versions after 8.2 according to documentation:

We’re changing this approach so that all user keys for new users (no changes for existing users) have the following format: JIRAUSER10100.

As it reads: "for new users" with the former account "janic" it did not happen (presumable created before version 8.2 was deployed on your system).

Also "belarirrc" is a older account. In case he leaves the company and comes back with "belarirrc1" you will see the same behaviour.

The full documentation was already linked by Kian.

[Prince Nyeche]

Hi @Megha Sinha 

It seems the userkey was changed to that string when the user was recreated even though the username is 'janic1'. If i'm not mistaken on Server you can change the userkey via API. have you considered such option?