Genaral Settings

Genaral Settings

The General Settings page, located under WorklogPro → Settings, is the main window where global in-app settings are configured. Any changes made here affect all users.

Screenshot 2026-02-26 at 15.42.35.png


Enable Timer

Screenshot 2026-02-26 at 16.13.06.png
Issue View Screen - Worklog Action when timer is disable

When the Enable Timer option is disabled, the timer feature is removed from the WorklogPro Action in the issue view screen.

If this feature is not enabled, users cannot use the timer functionality.




Work Description is Mandatory

When this option is enabled, users cannot save a worklog without entering a description. In other words, this setting makes the description field mandatory for worklogs.

If a user attempts to save a worklog without a description, the system will display an error message.

Show Detailed Permission Errors

When this setting is enabled, detailed permission information is provided in cases where issues cannot be viewed due to missing permissions in screens such as:

  • Timesheet

  • Calendar

  • Worklogs

  • Charts

  • Issue View

When the user clicks the exclamation mark ( ) icon displayed in such cases, a permission details table opens.

This table provides detailed information, such as:

  • Which issue or project is not visible

  • Which specific permission is causing the visibility restriction

Screenshot 2026-02-26 at 16.48.25.png

I have already migrated Tempo Worklogs

Enable this setting only after you have migrated your Tempo worklogs to WorklogPRO with the migration script. It tells WorklogPRO that the real author of each Tempo worklog has been written to the worklog's WorklogPRO property, so timesheets and reports can show those worklogs under their original authors instead of Tempo Timesheets.

See Migrating Tempo Worklogs to WorklogPRO for the script and the full migration procedure.

While the setting is disabled:

  • Tempo worklogs keep Tempo Timesheets as their author, because that is the author Jira itself stores.

  • They are therefore not listed on timesheets, reports, calendars and the Your Work screen when the screen is filtered by user or by team, since the worklogs do not belong to those users in Jira.

  • When the selected period contains such worklogs, a warning is displayed on those screens so that users know the view is incomplete.

While the setting is enabled:

  • Tempo worklogs are shown under their original authors, together with their original work descriptions and attributes.

  • Screens filtered by user or by team also have to query the Tempo Timesheets account, so they load more slowly while migrated Tempo history is present. A notice explains this when it happens.

Do not enable this setting before running the migration script. Without the migrated author information there is nothing for WorklogPRO to resolve, and the worklogs will still be displayed as Tempo Timesheets.

Default Duration Format

This setting defines the default time format of the WorklogPro application.

When configured here, the default time format is updated for all users.

Worklog Sort Order

It determines how worklog entries are sorted. The available options are:

  • Sort by Started

  • Sort by Created

Location of Worklog Action

It determines where the worklog action appears on the Issue View screen.

Available location options:

  • Issue Context

  • Issue Panel

The selected option defines the placement of the worklog action within the issue screen.

Maximum Team Members per User Group

Users can configure the placement of the worklog panel via the Admin → General page.

Screenshot 2026-02-26 at 12.21.05.png

This setting allows you to limit the maximum number of users that can be added to a Jira group. It also makes it easier to add a large number of members to a team.
If a user tries to add more users to a group than the specified limit, they will receive an error message.

Team User Restrictions

For a team, the maximum number of users that can be added manually is 400.
However, you can create a group and add up to 1,000 users to it, then add that group to any team. There is no restriction for this scenario.