Hi!
How do you or would you hide the work logs from clients? Currently, we work with tempo timesheets. I've disabled all the work log rights for my clients' user group, though still they receive e-mail updates and see the work logs under the 'all' tab in an issue.
How would I completely disable this?
Thanks!
If a user can browse issues then they have access to all of the details comments, history, work logs etc. So the only way to hide that information is to not provide browse access in the project.
In that case they would lose access to the boards and backlogs right?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We are having exactly the same problem at the moment. We have used a combination of 2 two projects, and issue level security in one of them. The first project is the tasks to be worked on and shared, with everyone having access. The second is mostly an internal tracking project, with some tasks that need to be assigned to the client - no time is logged against client issues, and the client cant see the issues we are logging time to.
Pretty clunky and causing us a little grief, so a solution that allows us to specifically limit who can see worklogs anywhere would certainly be preferred. I think this will become a more pressing issue for many before too long.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In our organization, we have two different Jira projects - one for communication with the customer (without work logs) and another for implementation tasks for internal employees with work logs. The customer does not have access to this second one.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That could be an idea, maybe we can automate the creation of the issues in the "shadow" project and link them. As long as the client has no access to the extra project, the link would be invisible for them but provide easy access to the team.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Hugo,
If you are referring the All tab in Jira issue view, this belongs to Jira that currently Tempo does not have access.
What Tempo does is for all worklogs that are created via Tempo, they will show as Tempo Timesheet author. For more information about this behaviour, please see the link https://tempo-io.atlassian.net/wiki/spaces/KB/pages/488931333/Why+do+the+worklogs+appear+with+the+author+Tempo+Timesheets+instead+of+the+user+s+name
Best regards,
Chih from Tempo Support
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Hugo Winder, you should probably set up a team inside Tempo Timesheets for all individuals working in this project, both internal and external. Then you can create different roles for internal and external people and grant them different permissions to be able or unable to view team logs as described here: https://help.tempo.io/cloud/en/tempo-timesheets/permissions-in-tempo/tempo-team-permissions.html
Hope this helps.
By the way, this is a requirement we have often received for our own app Report Builder and we will be implementing this in the near future. If you have any other special requirements, we would be happy to put them in as well, in case you are able and willing to try out another solution. Feel free to contact me for details. Sorry, had to mention it. ;)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Andreas Springer {Actonic}: Did you see my notes reproducing the visibility of logged work under the "All" tab of an issue, even when Tempo permissions were disabled for the user?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, but "View All Worklogs" is different from "View team worklogs", isn't it? I could be wrong...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Those two settings probably are different. My point is that both were disabled, and worklog entries were still visible.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Right, I didn't realize that. In this case I agree that it seems to be a bug.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In my experience, the Tempo "View All Worklogs" permission will control whether I can see all the worklogs for everyone, or just my worklogs.
@Hugo Winder Can you share the setting that you are using for that Tempo permission? It's in the Permission Scheme for the Project(s) of interest. For any Groups or Roles listed in that setting, please also clarify if the "clients' user group" is part of that Group or Role.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
These are my time tracking permissions, the project role 'Clients' is not in here.
Hopefully you have an idea
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Huh. I was able to verify that logged time is visible under the "All" tab on an issue, even if the "View All Worklogs" Tempo permission is not granted to a user:
@Hugo Winder: I would recommend that you report this as a bug to Tempo Support, and see what they have to say. It's possible they might not be able to fix it (if that worklog entry handling is too deep in Jira).
Click on "Submit a support request".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Dariya Chernologova mentioned the "Tempo Timesheets Access in Global Permissions in Jira". I checked that setting related to my test above. My test user did NOT have that either, and their logged time WAS shown as illustrated above.
So I continue to suggest that this is a bug. Logged time is visible, even with all available permissions in Tempo removed for a user.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, true. Looks more like a bug because the theoretical solution is not applicable or leading to desired outcome.
Interesting to know if there's still a fix to this. Maybe support team will suggest something.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Tempo Support confirmed what I outlined in my answer here:
Sounds like Tempo is classifying it as a "known limitation" (due to Jira requirements) rather than a bug.
I really like the Tempo product overall, so I don't mean to sound negative about it here. Jira users generally tend to ignore the "All" tab on issues anyway. But if you have a hard requirement to not expose that data at all, this might be a problem.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mykenna,
At this moment, Tempo synchronizes worklogs data back to Jira when users log time via Tempo.
Jira handles the All tab in Jira Issue view and decides what to display.
Best regards,
Chih from Tempo Support
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Hugo Winder
There are a few points that provide access to Work logs.
Please verify these 2 aspects for a Company managed project category.
Cheers,
Akbar.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @AKBAR , I haven't seen View all Work logs as an independent permission. Here is what I observe...
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.
yes. my point is that AFAIK there is no "view" worklogs permission. "Browse" is what governs the ability to view worklogs entries.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There is view worklogs permission on the system settings level, there you have to exclude their group, not only on the level of project permissions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Do you know what the setting is called?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Hugo Winder It might be Tempo Timesheets Access in Global Permissions in Jira. Otherwise you will have to go through the setup in Tempo specifically.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
yes. that is specific to Tempo.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear @Jack Brickey U didn't find the ''View all Worklogs'' permission because you may not be having the Tempo App installed. [My guess]
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.
Recommended Learning For You
Level up your skills with Atlassian learning
Learning Path
Jira Administrator
Configure Jira Software, Jira Core, or Jira Service Management, including global settings, permissions, and schemes.
Managing Jira Projects Cloud
Learn to create and configure company-managed projects in Jira Software and partner effectively with Jira Admins.
Learning Path
Become an effective Jira Software Project Admin
This learning path is designed for team leaders who configure Jira Software projects to match a team's processes.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.