Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Problem

Can it be configured to fine grained permissions who can create reports, or who can edit time logs of other users, etc.?

Solution

There is Edit All Worklogs Jira permission, to restrict who can edit time logs of others, and other related permissions, please see Jira documentation for more details.

As for viewing other users Timesheet, it is possible to restrict report visibility using Auditors Groups and Restricted Groups setting in app Configuration accessible using Gear icon in header part of the report page.

Timesheet Auditors Groups app configuration allows to specify user groups, who can see other users work logs.

Timesheet Restricted Groups app configuration allows to specify what user groups, currently logged in user can see worklogs of.

Thus Restricted Groups option allows to make it possible to see only “team members” timesheet, where team is defined by user group membership.

I.e, if anything is selected in Restricted Groups, report shows worklogs of users that are members of groups of the intersection of currently logged in user groups and worklog author groups.

In case of restriction applied, there is warning displayed in the bottom of the report, listing groups that are visible in result for currently logged in user. 

You may see https://docs.google.com/spreadsheet/ccc?key=0Ai6BFV79vBqqdFpNbGs2cHlvVlF0bVFYXzJDOWI2LVE for detailed information for how it works also.

In case of Timesheet Reports and Gadgets there is Auditors Roles setting additionally.

If Auditors Roles is configured, and user is not member of any of the roles selected, a warning will be displayed in the bottom of the report: Because of Auditors Roles configured data is limited to own worklogs for the following projects: KEY1, KEY2.

CAUTION, check carefully whether Classic Project roles and/or Next Gen project roles are selected, e.g. Administrators and Administrator. Because Next Gen projects use their own project roles, that may be named similarly to Classic project roles, you may need to select all roles with the similar names.




Didn't help? Find different article:


  • No labels