Custom Field Settings
Each custom field has a set of properties that not only affect the values that can be stored in the field but also influence its behavior. For default custom fields, these properties are pre-defined. When you add a custom field, you define these properties in the settings.
When you set these properties on the Fields List tab, you set the default behavior for the custom field. Properties for default values and empty values can be set independently on a per-project basis.
Settings for Simple Types
Simple types store data as a
float. Use the following settings to configure fields with simple types.
Stores the name of the custom field. Field names cannot contain the special characters
Determines what type of data is stored in the field.
For enumerated field types, the type is set when the field is created and cannot be changed. Simple types can be converted to another type that stores similar data. For more information, see Change Field Type.
When you select an enumerated type, additional settings that define the selected type are displayed. For more information, see Settings for Enumerated Types.
|Aliases||Assigns the field one or more keywords that you can use as a substitute for the field name in search queries and commands. For example, the aliases for the default Assignee field are |
|Can be empty||Determines whether the field can store an empty value. For fields with simple types, this option is always enabled.|
|Empty value name|
Assigns a value to show by default in the empty field. This lets you reference the empty value in search queries and commands.
When you edit an existing field, use the Empty Value setting to update this property.
|Make private||Restricts the visibility of the field to users with permission to view private fields. For more information, see Private and Public Issue Fields.|
Settings for Enumerated Types
Enumerated types store one or more values from a predefined set of values. These fields store references to an
build. Use the following additional settings to configure fields with enumerated types.
Enables the option to store multiple values in the field. This option is not available for fields that store a state type.
When you edit an existing field, use the Single value and Can specify multiple values toggle to update this property.
|Set of Values|
Assigns a default set of values that can be stored in the custom field.
This option is not visible for fields that store a
|Default Value(s)||Assigns a default value to the field. This setting is only available when you select an existing set of values. If the Multi-value setting is enabled, you can select one or more default values.|
|Can be empty|
Determines whether the field can store an empty value. You can only disable this option when a default value has been set.
When you edit an existing field, use the Can be empty and Cannot be empty toggle to update this property.
|Empty value name||Assigns a value to show by default in the empty field. This lets you reference the empty value in search queries and commands. If the Can be empty option is disabled, this setting is disabled as well.|
A condition for showing a custom field can be set up on a per-project basis. Conditional settings are only visible when you view or edit a custom field on the Fields in Projects tab of the Custom Fields Settings page.
Use the following settings to set the condition for showing a custom field in a specific project.
|Show only when||Determines which field is used as a condition for showing the custom field. The selection is limited to custom fields that store an |
|is set to||Determines which values from the field must be selected for the conditional custom field to be shown.|
To learn more about these settings, see Conditional Custom Fields.