Migrating from 3.9.x to 4.0.0

Owned by Deniz Oğuz
Last updated: Apr 20, 2020 by Ayse Basyigit
3 min read

In 3.10.0 version we have moved permission related settings from add-on specific “Permissions” page to “Permission Schema” of Jira. This will allow more flexible permission implementations. As a part of this, WorklogPRO adds following new permissions to “Time Tracking” section of project permission schemas.

  • Timesheet Approvers: Ability to approve timesheets of users. Only applicable if approval is active.

  • View Own Worklogs: Ability to view own worklogs made on the issues.

  • View All Worklogs: Ability to view all worklogs made on the issues.

  • View Worklogs of Private Issues: Ability to view worklogs made on the private issues.

  • Work on Non Editable Issues: Ability to log work on non editable issues.

  • Log Work for Others: Ability to log work for other users.

Also following settings are added to “Global Permission Schema”.

  • WorklogPRO Administrators: Ability to modify settings of WorklogPRO.

  • Use WorklogPRO: Ability to use WorklogPRO features.

  • Requiring Timesheet Approval: This is not a permission. Users who needs to submit their timesheet are specified using this setting.

If you upgrade from previous version of WorklogPRO, the app will try to migrate your previous “Permissions” settings to “Permission Schema” of each project or to “Global Permission Schema”. That means it will modify all permission schemas. You should check them after installation and be sure they are meaningful for you own situation.

Automatic Migrations During Update

  • Roles specified in “Timesheet Approval Roles” setting is automatically migrated to “Timesheet Approvers“ project permission. If there is no role specified on this setting “Timesheet Approvers“ permission is set to “Administrators” role if it exist. If you have renamed this role in your system this permission will be left empty.

  • “View Own Worklogs” is a new permission schema, previously there were no setting for viewing worklogs. We had used the Jira convention, if a user can view an issue he/she can also view worklogs. With this release we are adding a new permission for this. During the migration it is automatically set to the same permissions with “Browse Projects” permission. Note that Restricting worklog view is not always possible. Please check “Hide Time Tracking” section for more details about limitations.

  • “Hide Time Tracking” & “Hide from users in Selected Groups” settings are replaced with “View Own Worklogs” & “View All Worklogs” permissions. If you have “Hide time Tracking” setting turned on, we simply don’t give anyone “View All Worklogs” permission as a part of migration to be safe. Otherwise “View All Worklogs” permission is set to the same setting specified in “Browse Projects” during migration.

  • “Limit Groups That Can View Others' timesheet”: During migration we automatically migrate it to “View All Worklogs” permission.

  • “Limit Roles That Can View Project’s timesheet”: This setting is no longer available. You can use combination of “Browse Projects” and “View All Worklogs” permissions to control worklog visibility. We don’t perform any migration for old setting.

  • “Allow logging work on non-editable issues” is replaced with “Work on Non Editable Issues“ permission. If you have previously specified any project role for this setting they are copied to “Work on Non Editable Issues“ permission.

  • “Log Work For Others” is a new permission. Previously there were no permission setting for this, it was automatically given to users who has both “Delete All Worklogs” and “Edit All Worklogs” permissions. During migration we set this new permission to union of “Delete All Worklogs” and “Edit All Worklogs”.

  • “Groups That Can View Worklogs of Private Issues”: This setting is replaced with “View Worklogs of Private Issues” permission.