YouTrack Server 2022.3 Help

Value-specific Settings

Enumerated sets of values have properties that are assigned to each value in the set. You can edit a standard set of properties for any enumerated set of values.

To display these settings, click the Edit icon next to a value in the set.

type-specific settings for field values

Basic Settings

The following settings are available for all field types.




Assigns a name to the value.


Adds a description of the value. This property is not visible elsewhere in YouTrack, but can be used to explain the usage of this value to other users who might edit the set of values.


Assigns a color scheme to the value. This setting changes the appearance of the custom field based on the color that is assigned to the current value.

Type-specific Settings

Several field types have extended properties for values in the set. These properties are only visible when you edit the set of values that is used for the specified type.


Field Type



enum, ownedField, state, version, build

Indicates whether the value is archived, stored as a Boolean type. You can update this property directly in the list of values.

Values that are marked as archived are not available in the drop-down list for custom fields. This means that users cannot set the value for the field to an archived value directly in the user interface. If one or more values that are currently assigned to the field are archived, a user can clear the selection to remove these values from the field.

Archived versions are still available to commands, workflows, and the REST API. This means that you can use commands to add or remove archived values or update these values programmatically.

Assemble date


Stores the date when the selected build was assembled as a date type. When you use the TeamCity Integration, you can add values to the set and assign a value to this property automatically.



Stores a reference to the user who is responsible for the subsystem as a user type.

Use this setting to associate a specific user with each value in the set. You can then use this field to set values in custom fields that store a user type. For example, when you attach the Subsystem Assignee workflow to a project, the value for the Assignee field is automatically set to the owner of the value that is set in the Subsystem field.

Release date


Stores the release date as a date type. Can correspond to the actual or scheduled release date.



Indicates whether the version is released, stored as a Boolean type. You can update this property directly in the list of values.

This property affects the sort order in the drop-down list for the default Fix versions and Affected versions fields.

  • For the Fix versions field, unreleased versions appear at the top of the list.

  • For the Affected versions field, released versions appear at the top of the list.



Indicates whether the issue is considered to be resolved when it is assigned the corresponding value in this field. This value is stored as a Boolean type.

Additional Controls for Version Fields

When you view or edit the set of values for a field that stores a version type, these controls let you find and update specific values. These options have no affect on the behavior of the custom field.



Filter versions

Filters the list of values to match the filter criteria.

Show released

Toggles the visibility of versions that are marked as released.


Toggles the visibility of versions that are marked as archived.

Sort by

Sorts the list of values by name or release date.

Last modified: 21 April 2023