Hi,
We’ve encountered an issue where the team lead is not a user in certain projects and, as a result, cannot view the issues they are approving. This causes a scenario where the team lead approves worklogs without reviewing them.
A user reported time for an issue, but the worklog is not visible in the approval view. Additionally, the reported time is missing from the manager's Timesheet view total line, leaving the manager unaware of the missing or hidden log.
Worklog Details:
The worklog is visible via the Tempo API when using the getWorklog
query. In the API report, the status shows:
This is incorrect because the approver did not actually see the worklog.
Has anyone else encountered this issue? If so, how have you resolved it?
Hi @Renni Verho,
This is indeed a common complexity with Tempo/Jira permissions and people working across multiple (Jira) projects.
If you need your worklog approvers to be fully aware of all worklogs - which is an understandable requirement / assumption - , they will need browse project & view all worklogs permissions in all projects where work is happening. This is an additional permission requirement on top of Tempo Team permissions.
A common approach to this, is to create a user group in your directory for Tempo Approvers and grant this group these necessary permissions in your permission scheme(s). Or, if you want more granular control at project level, create a corresponding project role and add users to this role as needed.
Hope this helps!
Hi,
Project-level approvals are necessary for various reasons. The challenge lies in identifying projects where the approver does not yet have access. There were no warnings or indications that the approver approved unseen worklogs.
Is there a way to determine which project approvers need access?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.