Project Permissions

These restrictions are only enforced when performing operations using WorklogPRO UI. Using Jira’s REST API or by using other techniques, users may bypass restrictions. Worklogs are Jira’s own entities and Jira only controls its own built-in permissions. Technically there is no way to fully limit worklog operations as long as you use Jira’s own worklog entities.

Log work for others

Gives some users permission to log work for others. This permission is not granted to anybody for default.

If you enable this feature and log work for others users, author information of worklog will be set to WorklogPRO application itself. The user information will be stored on a worklog property. Our UI can handle this situation and can fetch the author information from the worklog property, but Jira Rest API will report the author field as WorklogPRO app itself.

Excluded from period checks

If a timesheet period is closed, you can’t log work for that period. You can remove this restriction from selected project users by using this new permission. As in the case of all Jira project permissions, you can update this permission based on user, group, project role etc.

View all worklogs

Gives permission to view worklogs that are registered by other users.

View own worklogs

Gives permission to only view worklogs that are created by the users themselves.

When the application is installed, the permissions "view all worklogs" and "view own worklogs" in all permission schemes are assigned to the ones selected in the "work on issues" permission. The same applies when a new project is created. The defaults specified for work on issues permission in the project are assigned for these two permissions.