Flavor configuration

The configuration dialog of a Flavor allows you to make global settings that apply system-wide for this field.

Open the configuration dialog by left-clicking on a Flavor > Configure.

Title

The Title field defines the name of the Flavor. The title is unique system-wide and is displayed wherever the Flavor is used — in task dialogs, project master data, and list views. The title can be changed at any time.

Description

The Description field allows you to enter an explanatory text that is displayed as a tooltip when hovering over the Flavor. This is especially helpful to communicate the purpose or expected values of a Flavor to other users.

Options

Lock settings editing

This option locks the configuration of the Flavor as well as all global settings. Only the person who activated the lock and administrators can make changes.

The following properties are locked:

• Title
• Type
• Color
• Configuration menu
• Visibility options

The lock is indicated to other users via hint icons. A request to remove the lock can be submitted.

Lock value editing

This option locks the value selection of the Flavor. Only the person who activated the lock and administrators may continue to edit the values.

Note: This option can only be activated if the option "Lock settings editing" has been activated first.

Value input required

This option defines the value input for the respective Flavor as a mandatory field. This is a global setting.

The property is only available for Flavors that are used in tasks or project master data. When the option is activated, the Flavor is marked with an *.

Usage in tasks: If a task contains Flavors with required value input, a check is performed when changing the status to the system status "Completed" to verify whether all mandatory Flavors have a value. If not, the status change is prevented and the user receives a notification. However, the task can still be saved or closed.

Usage in project master data: In project master data, a mandatory Flavor behaves in the same way — it is also marked with an *. Beyond that, the option has no further effect in project master data.

Tip: Create a dedicated group for the important Flavors with the "Value input required" option and place it as the first Flavor group. You can also use emojis to further highlight their importance visually.

Note: The validation also works when mandatory Flavors are displayed within linked project master data groups inside a task.

Define condition

This option allows you to define a validation condition for value input in the Flavor. It restricts which values are allowed — for example, requiring a number to be greater than 0 or within a specific value range. If an entered value does not meet the condition, the field is marked accordingly — however, saving is not prevented.

Sum from subtasks

When this option is activated, the Flavor's value is automatically calculated as the sum of the identically named Flavors across all subtasks. This is particularly useful for numeric Flavors, e.g. to aggregate effort or costs on the parent task.

Visibility

The Visibility dropdown defines which users can see the Flavor. The following options are available:

• Everyone — The Flavor is visible to all users in the workspace, including guests.
• Everyone (no guests) — The Flavor is visible to all "internal" users but is hidden from persons with a guest role.
• Specific people or teams — The Flavor is only visible to selected people or teams. All other members or guests cannot see the Flavor.

Context

The Context dropdown defines in which usage context the Flavor is applied. This affects, among other things, where a Flavor appears in the filter menu and the add columns menu. Additionally, the context determines whether a Flavor's value is displayed in a specific list view — for example, in the time evaluation, only Flavor values from Flavors with the Time context would be shown. The following values are available:

• None — The Flavor is not assigned to any specific context.
• Task — The Flavor is used in the context of tasks.
• Project — The Flavor is used in the context of projects and project master data.
• Status report — The Flavor is used in the context of status reports.
• Person — The Flavor is used in the context of person master data.
• Time — The Flavor is used in the context of time tracking.

Advanced

Copy GUID

In the Advanced section, the unique GUID (Globally Unique Identifier) of the Flavor can be copied to the clipboard. This ID is needed, for example, for formula Flavors, API integrations, or when troubleshooting with support.

Permanently delete Flavor

The Permanently delete button at the bottom of the configuration dialog allows you to irrevocably remove the Flavor from the entire system.

Warning: This action deletes the Flavor system-wide. It will no longer be available and will be removed from all objects (tasks, projects, status reports) in which it was used. This action cannot be undone.