Tempo, Error when logging time for other user

[Jason Thompson]

I am having problems with users logging time for other users in TEMPO.

We run Jira Data Center 9.17.2 & Tempo 17.9.0-jira-9.xx

A manager reported the problem first.
Every quater he logs time on another user, which although a user account, is just used for logging time against.
It is a JIRA Local DIrectory account.
When the mamager tried to log time for this other user in a ticket, he received the error message ...

Error! No "Log work for others" permission in destination project or "Manage worklogs" permission in a team with the worklog's owner as a member

The mamanger has JIRA 'Log Work for Others' permission for the project and the TEMPO Team 'Manage team worklogs' permission (& all the other Team permissions)
The user has the JIRA 'Browse Project' and the 'Work on Issues' permission for the project
I have checked both of these with the Admin Permission Helper.
The user account is also in a TEMPO team, where the manager is the Team lead.

I duplicated the setup in our JIRA test environmemt, setting myself up to be able to log time for the other user.
And it worked, twice even.
Then as a further test, I deleted one of the work logs.

Whilst scratching my head, thying to work out what was going on, I tried again to log time for the other user.
This was litterally a few mins later, I had not left the Timesheet, not changed any settings, nothing.
I got the same error message s the manager...

Any tips or suggestions greatly appriciated.
Log Work for Others Permissions for a Project
https://help.tempo.io/timesheets-dc/latest/log-work-for-others-permissions-for-a-project-in-t
Editing Team Permissions
https://help.tempo.io/timesheets-dc/latest/editing-team-permissions-tempo-server

[Marc - Devoteam · Accepted solution]

HI @Jason Thompson 

The only thin you could check are the logs as you are running on-prem, these might give you a clue what is happening.

Check this doc article as well https://help.tempo.io/timesheets-dc/latest/logging-time-in-a-timesheet-tempo-server 

Your settings seem to be fine as explained and in alignment with Tempo documentation.

If there is no obvious issue and the logs don't tell anything, I suggest to contact Tempo support and provide them with the issue

[Jason Thompson]

Hello Marc,

Thanks for your quick reply.

I will as suggested, have a look in the log files.

I suppose at least it is good to know that I have not missed something simple.

The behaviour seems a bit buggy, sometimes it works, sometimes not.

If I learn anything further, I will be sure to update here.

[Volohov]

Hello, I have the same problem even on 18.0.0-Jira-9 version

Jira version is 9.12.14

[Roberto Bacchini]

Hi all,

we're in the same situation!

We're running:

• Tempo 17.9.0-jira-9.xx
• Jira v9.12.12

In a test environment we have a different tempo version (Tempo 17.8.0), an the issue is not present.

[Marc - Devoteam]

Hi @Roberto Bacchini 

Reach out to Tempo support and make them aware, as this might be a bug.

[parthiban_selvaraj]

Hi all,

In cloud also we are facing this issue.

Thanks,

Parthiban

[Victor Rochet]

Plop,

Same there with

- Jira Software 9.4.14 (Data center)

-Tempo Timesheet 17.9.2-jira-9

[Jason Thompson]

I opened a ticket with Tempo support.

They said ....

"We have released the fix for this issue in our latest release, please try it out and let us know if that did not resolve the problem in your case. In the meantime, we will be setting this request to resolved. But you can always contact us if you encounter any other problems.

Best regards,
.... from Tempo Support"

I have however not yet tried the latest version out, but hopefully solved.

[Victor Rochet]

The issue was coming from Tempo it self, other instances were impacted.

We had to upgrade the plugin to  18.0.1

After some test we conclued that the issue is solved.