How do you restrict worklog viewing access in Tempo Timesheets to approvers or team lead?

Chris Ranglas July 21, 2017

We have upgraded to latest version Tempo Timesheets on JIRA server 7.2.xxx, and now approvers can not see time of people on their team. We have about 90 tempo teams. How do we make it so approvers can see JUST their teams work logs? We know we can modify permission schemes so that a group of managers can "view all worklogs" but we do not need all managers to see everybody's worklogs.

2 answers

1 accepted

1 vote
Answer accepted
Taylor Noreply August 18, 2017

Tempo Timesheet permissions  have been moved to JIRA project permission schemes with the release of Tempo Timesheets 8.1 (release notes here). So that means Tempo does not override any JIRA permissions any more. The "Approve timesheet" permission does no longer give you the permission to view the team member worklogs within Tempo.

The only way to restrict now people from seeing each other worklogs is to split your single JIRA project into many JIRA projects. The "View all worklogs" permission of your JIRA project permission scheme should be assigned to a specific JIRA project role to avoid the necassarity to create a new JIRA project permission scheme for all of those new created JIRA projects.

Thanks and regards

0 votes
Athena Petridou [Nimaworks] July 28, 2017

Hey Chris, 

 

You can achieve this by changing the permissions of the teams, not of projects.

Go Tempo -> Teams -> Choose Team -> Configuration -> Permissions 

There, change the browse and approve permission with your manager's name for each team. 

 

I hope I helped. 

BR, Athina

Chris Ranglas August 8, 2017

Hi @Athena Petridou [Nimaworks]. thanks for the suggestion. what you described is how we configured JIRA/Tempo back in fall of 2016. We recently upgraded to latest Tempo version so the people with browse and approve permission can only see if you go into new Tempo persmissions in JIRA and grant "View worklog access" as well. When we do this however, it opens up view access to everyone since we use a common permission scheme accross our projects.

Suggest an answer

Log in or Sign up to answer