Skip to main content
Tasks

Tasks settings, types, objectives, and statuses

Administrator classifiers, rules, notifications, and module settings.

Last updated 20 days ago

Administrator-managed classifiers, default values, completion rules, notifications, and time settings.

Tasks settings

Tasks settings are modified by a user with administrative rights. The settings area allows for the management of:

  • general module operation and optional features;
  • Tasks types;
  • objectives;
  • statuses and their sequence;
  • default comments;
  • modal notification rules;
  • templates and Tasks sets;
  • options related to notifications, time, approval, or finances.

General settings also allow for the management of the default Task duration, full-day working hours, automatic creator assignment, mandatory comments upon completion or cancellation, completion questions, and the automatic stopping of active timers at the end of the workday.

A modal notification rule can display additional text when the Tasks matches a selected status, type, or other condition defined in the rule. Lists of types, objectives, and statuses are part of the organization's configuration; therefore, their names may vary across different accounts. Note the current value before changing the setting. After making the change, verify its impact using a test task. Changes to settings may affect all users in the organization as well as newly created items.

Where to find administration areas

Open the system administration menu and select Tasks. Depending on the configuration, this section may include general settings, types, objectives, statuses, default comments, modal messages, templates, sets, and completion questions.

Types and objectives

A Type describes the form of work, such as a call, meeting, or reminder. Types can be used in list tabs, filters, color coding, and automation rules.

An Objective describes the aim of the activity—such as a sale, a service interaction, or an internal work outcome. When creating a value, use a short, clear name. Check for usage in existing records before deleting it.

Statuses

A status defines the workflow progression and forms the columns of the Kanban board. Establish a clear sequence from the initial to the final status, and configure colors, activity status, and other rules available in the form. After changing the sequence, verify the display in both the list and Kanban views.

Default Comments and Modal Messages

A default comment allows for the quick selection of frequently used text. A modal message displays additional instructions when Tasks meets specific conditions, such as a particular type or status. Test the rule using a single Task record and revert it to its original state after testing.

Changing General Settings

Modify one value at a time. Note the initial state, open a new Task form, and verify the result. If the setting relates to completion, test it only with a test Task record. Revert the organization's setting to its original value after testing is complete.

Completion Questions and Mandatory Comments

Default completion questions can be enabled in the Advanced or Maximum plan. These questions are linked to Task types. When completing Task, a form is presented, and the responses are saved as a system comment prior to the final status change.

Specific toggles may require a comment when completing or cancelling Task. In the standard interface, the comment must be entered before the status action is performed. These rules must be tested both in the primary card action and in other status-change interfaces.

Automatic Creator Assignment and Timer Stopping

When automatic creator assignment is enabled, the user creating a new Task is pre-selected as the responsible party. This prevents situations where the creator cannot see their own unassigned private Task.

The automatic timer-stopping setting is designed to terminate active timers at the end of the organization's workday. It relies on scheduled server tasks, the end-of-workday setting, and the time zone. Before enabling it, verify the actual stop time and the system's behavior if the scheduled execution window is missed by using a test timer.