The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Can time booking (worklogs) be accessible only to team members in a public project?

P_
September 11, 2020

Our company uses Jira and Tempo timesheets.

The problem is as follows: we need to work with time estimates, and we need to book our time in JIRA. However, nobody outside of a project should be able to view the actual values (like how much time I spent yesterday), even though they still need to have access to the project and see all the tasks.

So for example, I need my colleague from  project B to browse freely through project A, but not seeing time logged.

I have some doubts that this is even possible because Time Spent, or effort estimation related fields in general, are used on various places, so the information could be only partially hidden.

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Alexander Eck [Tempo]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
September 11, 2020

Hi,

in general this is all doable. Jira has the option to restrict worklogs by giving the "view all worklogs" permission on a JIra project permission scheme. That would need to split project A and project B into two permission schemes.

With Tempo you get another layer on top of that which enables you to restrict permissions on team level. That is helpful when multiple teams work on the same project.

As worklogs also feed into the activity stream you would need to disable this view.

BR

P_
September 11, 2020

Thanks, but then I guess there is a problem: let's say there are hundreds of projects (actually, this is the case) and new projects are being created daily. Creating a permission scheme specifically for each of them is impossible. I was hoping for something like a scheme that by default limits worklogs for team member only.