Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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

Screen Shot 2021-01-07 at 7.56.14 PM.pngScreen Shot 2021-01-07 at 7.57.17 PM.png


Instead of userId 'janic1' its showing JIRAUSER114400.

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

2 answers

0 votes

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?

0 votes

@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.

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 Community Leader Jan 07, 2021

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.

Like Megha Sinha likes this

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira Software

Presenting the "Best of 2020" Jira Software roundup!

Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...

7,071 views 8 28
Join discussion

Community Events

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

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you