Forums

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

TimePO User Timesheet Report Permissions

JosephS February 11, 2015

First, nice add-on. Thanks. The User Timesheet Report does hit the spot with having a need for managers to see an overview of where was time spent by staff - especially when contractors are involved.

Since activating this add-on, I notice that I, personally, can see multiple users in a User Timesheet Report, but when another developer or team lead tries to run the same report, they only see their own time.

Is there a permission that controls the level of reporting?

I have administrator privileges, others are project leads, others just developers or users. Not sure what specific permissions does this.

Thank you.

5 answers

1 accepted

0 votes
Answer accepted
Artsiom Siamenchykau
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 16, 2015

Hello,

Project leads are to be JIRA Administrators as well (not JIRA System Administrators). 

If it is not alligned with you process, we can develop any specific permission scheme for your team and will be glad to discuss it with you.

Thanks for using our add-on. 

 

Best regards,
Artem Semenchikov,
Founder, Synergy Apps
0 votes
Daniel Boczek
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 1, 2016

This restriction does not make any sense because users can't see in report data which otherwise they can see in Work Log tab of the issue (according to visibility user selected when adding a Work Log).

When user logs work on issue he can choose it's visibility I think report generation should takie this information into account. There could be filter though to generate report only for current user or all work logs I can normally see in Work Log tab.

If not the above then at least maybe there could be separate permission which by default could be added to Administrators but anyone will be able to add it to other Roles, users, groups etc. Such change will be backwards compatible. Anyway I think visibility set on Work Log should be respected.

 

Thanks.

0 votes
JosephS October 6, 2015

I agree. It seems solely tied to the one "Administrators" role in JIRA. It is unfortunate it does not look for a second one which could be customized to users that we do not wish to be JIRA administrators too.

0 votes
Henrikas Simonavičius
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 5, 2015

I had permission-related problems with addon because I've created custom project roles and removed default JIRA roles. After experimenting I've figured out:

  • if project role "Administrators" is removed or renamed, addon will stop working. It throws an exception when generating report
  • Only users in "Adminstrators" role can view worklog of other users. I've created a new project role "Project Administrator" with administrative permissions and assigned it to myself, but could not see anyone except me in the reports. Renaming the role to "Administrators" fixed the problem

Seems like this addon is bound to specific string "Administrators" rather than based on permission set?

 

0 votes
JosephS February 24, 2015

Well, we have managers and leads that really are not meant to be JIRA Administrators. We do not want them to have the permissions to various actions in JIRA that our Product Owners and true "administrators" do. They are resource managers and technical team leads who should have the means to see the timesheet report for anyone working on that project. This is similar to what is described by the add-on to give managers this capability.

If there was a specific "group" that the add-on would provide this permission to (e.g. "TimePO Managers"), then I can create this group and add the appropriate managers and leads who should have the permission to see the team's timesheet on top of their own.

Thanks again. For the basic use for each individual, it has helped.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events