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.
Can approve timesheet
Grants permission to approve or reject timesheets.
For more information, visit:Approval Permissions
Requires timesheet approval
Grants permission to submit timesheets for approval. For more information, visit:For more information, you can visit this page; Approval Permissions
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.
This permission is typically granted to an authorized person within the company, for example someone from the Finance, HR, or Project Management Office (PMO) department. Users who have this permission can log work on behalf of all other users for periods that are marked as closed. They are also excluded from time-based worklog restrictions, meaning they can create worklogs without being affected by forward or backward time limitations.
View all worklogs
Gives permission to view worklogs that are registered by other users.
View private issues
The ‘View Private Issues’ permission allows a user to see all worklogs of private issues only if they also have the ‘View All Worklogs’ permission. If the user does not have ‘View All Worklogs’, this permission is ignored. Without this permission, users can see only their own worklogs on issues marked as private.
When the application is installed, the permission "view all 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 this permissions.
Project permissions are handled differently in Team-managed projects. For more details, please visit this page.Accessing WorklogPRO Permissions for Team-Managed Projects
Jira Permission Matrix-Private Issues Scenarios
The table below lists the permissions a user has in the projects.
Projects | View All Permission | View Private Issues Permission |
|---|---|---|
Project A | ✅ | ❌ |
Project B | ✅ | ✅ |
Project C | ❌ | ✅ |
Project D | ❌ | ❌ |
The table below shows the worklog visibility results for an issue that was marked as private in the issue settings page for each of the projects listed above.
Projects | Visibility Result |
|---|---|
Project A | Can see own worklogs only (no ‘View Private Issue’ permission) |
Project B | Can see all worklogs, |
Project C | Can see own worklogs only (no ‘View All’ ) |
Project D | Can see own worklogs only (no ‘View All’) |
In Brief:
With ‘View All’ + ‘View Private Issues’ → Can see all worklogs of private issues
Without ‘View All’ → ‘View Private Issues’ ignored, can see only own worklogs