I do not want my users to see other people's logged time / worklogs. Therefore I would like to restrict access to the project report.
I found no permission setting that would allow me to do that. I found a module to disable the dropdown in the Tempo JIRA topnav bar, but all reports are still available from the timesheet view.
Hey there, Fabian.
I would recommend you to contact the plugin vendor directly so that you can have your questions answered quicker. Review the following information:
Hope this helps.
public boolean showReport()
return // Add condition who i.e. Project Role , Group, User can view report.
//eg.return (ctx.getUser() != null) && (ComponentAccessor.getCrowdService().isUserMemberOfGroup(ctx.getUser().getName(), "jira-administrators"));
I did configure it so nobody can see other peoples worklogs. However, the project report still shows other peoples logged work :(
Our managers are complaining that this is a privacy issue.
I was not able to resolve this using the permissions neither by disabling modules.
All users who are in team leader role in Tempo will see worklogs of all users in the team member roles given that they have browse permission for the project in JIRA.
Please verify your team configurations
I guess there is some misunderstanding here. Only team leaders can view other users worklogs in Tempo project report. Team members can view own worklogs in project reports and the total sum of other users logged work in the project timesheet. The above is the default behavior in Tempo.
There is also an option to restrict the view for team members by selecting a project role as documented on this page
If the above does n answer your question can you attach a screeshot of your problem here or in a private support issue in our support channel.
Please read the documentation page for the Project Role as mentioned earlier herehttps://tempoplugin.jira.com/wiki/display/TEMPO/Project+Role+to+View+Other+Users
and see the two two screenshots after this text
Screenshot: The Project Timesheet with the default option No Role Set as view by Team Members (Paul Bergen)
Not very intuitive and also I could not find it when I crawled thorugh your documentation.
Whereas it seems to answer the question, there is a major problem it:
According to German law, only the direct supervisor is allowed to access this information (because he has to) but nobody else.
Following your suggestion, I can see two scenarios:
Either way, there is a big problem with it, because Greenhopper requires every SCRUM master to have the “Administer Projects” permission for all projects his team is working on. This means for the two scenarios:
This is a big concern to us, because it means that we cannot use Tempo in our company because it does not meet the legal requirements in Germany.
We need to have the ability to enable the group of people who can access other people’s worklogs on a global administration level and not on a project administrator level or we need to be able to completely disable the project report.
The correct way would be to create a new role (Time Tracking Admin) and only give the direct administrator this role. But like you said, if you have 30 people with project admin permission, then they can add themselves to this role. So we need to look at why you need all these users to have project admin permission. The requirement from GreenHopper that Scrum masters need project admin perission is the problem here. It would be much better if GH would allow you to also specify a "Scrum Master" project role.
Given this information, I don't see how Tempo could achive this problem with GreenHopper. Project Roles is the best configuration option to contol this kind of permissions and in my opinion, requiring every Scrum Master to be project admin on all projects is the source of the problem. This behaviour in GreenHopper breaks any plugin that uses project roles for permission handling because you said, the project admin can simply give himself the permission he wants.
It is a big concern to us as well that GreenHopper can't operate without opening up permissions configurations as you described. There is already an issue for this in the GreenHopper project, GHS-4701. Lets continue this discussion there.
Thanks for pointing this out,
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
...there's anything I've learnt from working, it's that people are lazy! No offense to anyone reading this, but it's true and we can all admit it. The easier you make something for someone, the more...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG