Only JIRA Administrators and JIRA System Administrators can configure Timetracker. |
On these pages, you can configure the behavior of the Timetracker. To open the Timetracker Global Settings:
|
Administrators can choose whether worklog description is mandatory or not for Timetracker users. By default, a description is optional.
You can enable or disable displaying the results of the previous (or the default) query on Reporting pageload.
By default, every reporting page load queried the results based on the previously selected criteria for the current user. This option lets the administrators turn this behavior off and prevent queries on pageload. We recommend our customers with large instances to turn this off when they experiencing problems on pageload.
You can enable or disable displaying the Timetracker section on Issue view. Totals and details of other users' worklogs logged to the issue are displayed on the Issue screen for the selected month. By default, this option is enabled.
Here you can define the maximum loggable hours per day for Timetracker users. Empty field means there is no limit.
Eg.: 6, 8 or 6.5
This feature is designed to manage non-working, non-billable issues, to provide credible reports. This feature can be useful if you have a dedicated project or issues for non-work activities, eg. for lunch.
The administrator can define a list that may contain issue keys and regular expressions. This list will be the list of non-working issues. The issues listed here are ignored when creating the Real Work Summary.
By default, the Non-Working issues list is empty.
Timetracker's many features behavior depends on whether the given day is a working day or not. By default, all weekdays are working days while all weekends are non-working days.
Normally, all users have to fill at least as much working time (hours) for each working day as is set in the "Time Tracking" settings. In case a user did not work as many times as expected, they can use the configured non-working issues to fill the day.
You can add days that are weekdays but not working-days (For example: public national holidays):
You can remove the dates by clicking on the X on the label.
You can add days that are weekends, but working days:
You can remove the dates by clicking on the X on the label.
Here you can enable this restriction and configure the period in which the users can log or edit work.
You can define the days (0-365) that users can log work or edit existing worklogs in the past or in the future.
To allow a user to log work only for the given day, enter zero in both fields.
In the Permission Settings you can add groups for which this is will be not valid and they will still be able to create/edit worklog in the configured period.
This restriction can be useful after disabling the other Log Work options in Jira, otherwise, it can be bypassed. |
Here you can define worklog attributes here. Users can only use attributes that are defined here!
Make Worklog Attributes mandatory so it always has to be filled with at least one pre-defined attribute