Problem
When logging time on behalf of certain users, the process fails with a generic "Something went wrong" pop-up. Everyone who tries hits the error for the same specific individuals, while logging time for other users works.
Solution
This is common with newly invited or external users. Please first make sure the usual permissions are in place: the person logging time has Log Work for Others in the space, and the affected users have Tempo Timesheets Access and Work on Issues. If those are correct, the likely cause is an Atlassian platform limitation (ECO-1507).
On Forge-based sites, logging time for another user requires that user's email address to be verified in Atlassian. The earlier Connect platform could act on behalf of users with unverified emails, but Forge can't, so the action fails. A user's email is verified when they accept their invitation and complete account setup, or when they log in to Jira.
To confirm, check whether the affected users have accepted their invitation and completed account setup. A user who was added to a group or space but never accepted the invite is a common case.
This isn't something Tempo can change. Until Atlassian resolves it, the workaround is for each affected user to accept their invitation or log in to Jira once. They can then enter their own time, or others can log time for them.
If the error continues after the user has verified their account, please open a support ticket with a HAR file captured while logging time for both an affected user and a user it works for, in the same session. See Creating HAR and Log files for support.