Settings

Timezones

You can set which timezone you and your team members work. This timezone will be treated as default timezone for new members as well. This will be considered while calculating ETA of projects and tasks. (You can also override timezones on user basis if needed. For example if someone works from different timezone than the space timezone)

Work day closing time

Specify what time does the work day closes (for example 5pm). This helps scheduler to plan tasks accordingly and not move tasks to next day if needed. (You can also override this for each member basis if needed)

Working days

Specify which days are working days in a week. You can also override this setting for a member basis if needed. This helps scheduler to create timelines and calculate ETAs.

Working hours per day

Set default working hours / productive working hours per day. Depending on your company setup, you can define what are the productive working hours for a member. Generally in a work day of 8 hours, 4-5 hours could be treated as productive working hours. These hours are crucial in ETA calculation.

Default estimated hours for a task

By default scheduler ignores the tasks which does not have estimated hours set. Using this setting, you can set the default estimated hours for tasks without hours.

Override settings for each member

For example you are working with a contractor or a part time member. You could override timezones, working days and working hours for that particular user. This helps the scheduler to come up with realistic timelines and ETAs.

Workflows

There are 4 states in Workflow: Not started, Started, Completed, and Cancelled. You can also create additional statuses here and define status colors accordingly.

• Scoping: This is a special status, and tasks under this status are not shown to assignees in their upcoming tasks view. Tasks under this status mean that the requirements are not yet complete, and this task is still being planned.
• NOT STARTED: Any new tasks that are todo and have not actually been started by the assigned user. These tasks are included in the ETA calculation of the project.
• STARTED: Tasks that have been started or are in progress for the project. These tasks are still included in the ETA calculation of the project.
• COMPLETED: Tasks that have been completed. These tasks are not included in the ETA calculation of the project. Statuses like In Review, Pending, Waiting for Approval, and Done are examples of completed statuses.
• CANCELLED: Tasks that are on hold or cancelled. These tasks are not included in the ETA calculation of the project. Examples include On Hold or Cancelled.

When creating a custom status, it's really important to choose the right category. For example, if you create a new status called "Waiting for Client", but choose the "STARTED" category, tasks will still not update the project progress and ETA.

Upon status deletion, any task that belongs to the deleted label will be moved to the nearest appropriate label.

Labels

Labels are used to categorize tasks if needed. By default, there are 2 labels: Bug and Feature Request. However, you are free to add new labels based on your requirements. Labels help you filter tasks based on your use cases.