This is the documentation for the next major release of Tempo Timesheets and is a work in progress.
Please go to the Space Directory to view documentation for released versions of Tempo Timesheets.

Skip to end of metadata
Go to start of metadata

This page explains the Time Tracking Permissions and Validation options as part of Tempo Timesheets Global Configuration.

To open the Global Configuration: 

  1. Log in as a user with the JIRA Administrators Global Permission.
  2. Select Add-ons from the Administration menu (cog icon: ) at the top right of your screen. Then scroll down to Tempo administration left tabs and choose the Global Configuration option.
    (tick) Tip: Use Keyboard Shortcut instead: g then g and start typing Global Configuration.

The Time Tracking Permissions and Validation options in Global Configuration

Each item from the screenshot is explained in the table below.

Table: Time Tracking Permissions and Validation explained

OptionDefaultDescription
User with Approve Timesheet Permission can log work for team membersNoIf enabled, users with the Approve Timesheet permission, can log work and edit hours for all their team members.
User can not log work on parent issuesNo

If enabled, an error message is displayed (in the log work dialog) when a Tempo Timesheets user tries to submit a work-log for an JIRA issue with sub-tasks.

Log work with start timeNo

If enabled, a Tempo Timesheets user can set start time when logging work. Note! A useful reading on the difference between my JIRA worklog and my Tempo worklog.

Remaining estimate is optionalNo

If enabled, and an issue has no Original estimate, the Remaining estimate is not calculated in the time-tracking entry. Again if enabled and an issue has Original estimate, the Remaining estimate is reduced by the time spent until the value 0 is reached. The Remaining estimate can not be a negative number, but if it has reached 0, the user can add a new one.

Worklog description is optionalNo

If enabled, and no text is written in the Log Work Description field, a default text Working on Issue $key is added. As with any text in the Log Work Description, the default text can still be edited.

Allow logging on closed accountsYes

If disabled, it is not possible to log work on an issue that has an account in closed status.

Allow logging on not editable issuesYes

If disabled, and the jira.issue.editable property is set to false in the JIRA workflow status, a Tempo Timesheets user can not log work.

(info) A few notes:

  • This property is false by default in the JIRA workflow for issues in Closed status.
  • If enabled the workflow status must have a transition to Reopened status as in the JIRA default workflow. The user must also have a permission to execute the reopen transition.
  • The workflow transitions can be hidden, by using the Hide Transition option in the JIRA Misc Workflow Extensions plugin, if you don´t want users to reopen issues.
  • There is also an option to use the jira.permission.work.denied property as documented on this page
Max hours per day per userUnlimited

If a limited value is selected from the drop-down list, the lowest value is set as the Hours per day in JIRA Time Tracking settings and the highest value ends in 24 Hours. The values increment by one hour from the lowest to the highest.

Users allowed to register time into future90 DaysOther options, rage from 0 Days to 360 Days. 0 Days means the user can not log work for Tomorrow. 360 Days means that the user can not log work on a date that is over a year from current date.