Mandatory Work Log Description

Administrators can choose whether worklog description is mandatory or not for Timetracker users. By default, a description is optional.

Results on Reporting pageload

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.

Display Timetracker section

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.

Timetracker Gadgets

You can enable or disable displaying the Timetracker Gadgets on Dashboards. By default, this option is enabled.

Issue Picker

Here you can choose to allow users to log their time to only one or more issues at a time.

Maximum loggable hours per day per user

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

Maximum number of Issues to query

Maximum number of selectable worklog attributes

Non-working issues

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.

Configuration

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. 

Example

• Use issue keys, eg. MYPROJECT-1, MYPROJECT-2
• To set up all the issues of MYPROJECT to be Non-working, the following regular expression needs to be used: “MYPROJECT-.*”

Exclude date

You can add days that are weekdays but not working-days (For example: public national holidays):

1. Click on the input field on the right side, or on the calendar icon.
2. Write or select the desired date.
3. Click on the "Add" button.
4. If the date and its format is valid, it will be added to the list of dates on the left.

You can remove the dates by clicking on the X on the label.

Include date

You can add days that are weekends, but working days:

1. Click on the input field on the right side, or on the calendar icon.
2. Write or select the desired date.
3. Click on the "Add" button.
4. If the date and its format is valid, it will be added to the list of dates on the left.

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.

Here you can define worklog attributes. Users can only add attributes when logging work that are defined here.

• The maximum length of an attribute is 50 character
• You can not use "," in the attribute name and we recommend to avoid special characters
• The added attributes will show up under the input field
• You can change the order of the attributes by drag&drop each row. The attributes will be ordered in the picker for the users based on the order configured here.
• You can edit each attribute's name.
• You can also disable these attributes, which means that these attributes will still appear in the reports and searchable, but new worklogs can no longer be added with these attributes.
• You can delete any of the attributes anytime

Make Worklog Attributes mandatory so it always has to be filled with at least one pre-defined attribute.