Document toolboxDocument toolbox

To learn more about Tempo products, please visit our Help Center. For support, see our Support Portal.

Username changed but it does not update in Timesheet and in REST API's

QuestionThe user has changed the username in JIRA, but the Tempo Timesheets reports still show the old one. 
Answer

The userkey is an unique identifier created automatically when the user is created in the JIRA instance. This key is created by Jira, not by the user, their admin or Tempo. The key is not related to changes that the user can make to his name in the JIRA instance. The key will remain the same, even if the user's name has been changed. This is done in a way to keep the data associated with the correct user as different users can have the same name (i.e. John Smith).
In earlier versions of Jira (before 8.2.) the user key was the same as the username in lower key. Since the release of Jira 8.2, the user key for new users is in the format JIRAUSERXXXXX (e.g., JIRAUSER11000).

In the reports, we display the userkey that is generated by JIRA. That's why when the user changes his name, the key remains the same and this is not changeable.

For example, John was first created in Jira with "john" as username and userkey. Then we changed this username to "Taylor". The original userkey will remain as "john" even though, through the UI he's been identified now as Taylor. 

As a workaround, for REST API calls, you can run Jira REST API to get the user's details with userkey.https://docs.atlassian.com/software/jira/docs/api/REST/9.1.1/#api/2/user-getUser