Recently, in JIRA I have updated a couple of usernames as they were not set as per my standards of using company email IDs as usernames. Even after updating them I still get the old username formats in the exported reports.
Example: My Username was setup as vinay.poosa and I have updated it to vinay.poosa@JIRA.com. When I export my worklog details from JIRA to excel I still see my username as vinay.poosa but not as vinay.poosa@JIRA.com
Am I missing any steps here? Can someone please help with this?
Thanks much in advance.
Hello @Vinay Poosa
Have you tried re-indexing? Your database need's to be "updated" with fresh data, that's why when you make changes you re-index changing your username is one of those.
Here is documentation, but if you are doing this first time I recommend "Background re-index"
Here is a explanation from Atlassian
Quoting Andy Heinzer (Atlassian Team) from https://community.atlassian.com/t5/Jira-Software-questions/Wrong-user-name-reference-when-renaming-username/qaq-p/665936
"You are not expected to be able to change this field in the jiraissue table. Actually the value in the jiraissues table is correct. I understand why you might believe it to be wrong, but that is because of the way Jira is tracking user account renames.
Jira tracks a user account being renamed inside the app_user table. When an account is first created in Jira the user_key field is set to match the cwd_user.user_name value. However after this account is first created, that user_key field is never expected to change in the Jira database. Regardless of whether or not the username changes, that user_key remains constant for that particular user account. Instead the app_user.lower_user_name value can change to correspond with the changes in cwd_user table when the user gets renamed, but there are several places within Jira that do not directly refer to the cwd_user table for the user account. Instead Jira is primarily looking at the app_user.user_key entry for historical records such as which user updated an issue, or executed a transition. This can also be seen when you look at the issue details view in Jira, if you click on the history tab, this view shows the app_user.user_key field for a username, and not the cwd_user.user_name field.
This way Jira can keep track of historical changes that take place through a specific account, even if that account's name changes over time. "
You are exporting tempo work logs or standard Jira work logs?
Can you export by full name instead of username?
Sorry for not responding sooner, I was trying this add -on my self
So I didn't do any changes to the "basic setup", I exported the report to Excel there is a column "Worklog Author(Full Name)" this field/column should contain the author's full name, not the username, can you check your report, please?
Hi @Olga Videc No problem. You are correct. When we export the report to an excel file there are two sheets in the file, in the first sheet which is named as 'Worklog" there I see a column called "Worklog Author(Username)" and "Worklog Author(Full Name)" and I get the updated details in these two columns. But, the actual issue is in the second sheet which is named as Users, where the Username is still showing as old or something like JIRAUSER*****, see below screenshot. This is the report which I'm looking for.
Look like app is pulling "user_key" not "app_user.lower_user_name"
When you create a user your user_key is set to your username and it's never going to change in DB when you change your username "app_user.lower_user_name" changes not "user_key" (I know it's not easy to understand)
Explanation by Atlassian team expert
I'm investigating further, I'll get back to you.
Hello @Vinay Poosa
I spoke with dev/support from the WorkLog app, it's a known bug that is already fixed and will be released soon, they expect to release it sometime next week.
The new excel report will contain both username and user_key(this the old username) because of backward compatibility.
What that means is you will see a column containing "old username" but there will also be a column with "new and accurate" usernames, and user's full names will be included.
The bug is fixed in 4.8.2 release, you can expect it sometime next week.
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