How Tempo handles Jira user changes

This article is for Tempo for Cloud and Data Center.

In a nutshell: user management is handled by Jira, and Tempo complies to any changes done by Jira. When a user changes their email address, or is generated by external user management tools (i.e. Active Directory, LDAP), Jira treats them as a new user with a unique Jira AccountID. Therefore, Tempo is also not able to recognize them as the same user account even if they have the same user name. In this case, there are 2 ways to handle the user’s worklogs:

Keep the old user account and run necessary reports prior to disabling the user account, then start logging time with the new user account from this point onward.
Move worklogs from the old user account to the new user account, either by manually creating and deleting them individually through the Tempo UI, or by updating them through the Tempo REST API https://apidocs.tempo.io/#worklog.

On Data Center, it’s possible to modify the worklog table directly; however, it’s recommended to do this if the database backup has been done.