Depending on whether the field is predefined or user-defined, different settings can be made here. For predefined fields, it is not possible to change the type of the field.
The following field properties are available:
_-(),.
and may only occur once in the system.Date
or Date with time
): If this option is activated, this date/time will be used as a local date: it will always display exactly this local date/time for every user, regardless of their time zone. Otherwise, this value is interpreted as an exact time that is displayed to every user in their time zone. Selectable values
): A list of values that can be selected for this field is stored here. A distinction can be made here whether a value can only be selected for the supporter or also for end users.External link
): The link and the title to be displayed are specified here. The values of the other fields of the ticket can be used with placeholders. The key of the field is always used in curly brackets {
and }
. Additionally the fields of the ticket owner can be used by using {ticketowner.
plus the key of the user-field.https://www.server.domain.com/access/query={identifier}
https://www.server.domain.com/access/query={ticketowner.room}
/ticketlist/view/itilmaster.ticket{ticketId}
External link
, the link is always auto-created from given placeholders.resourceid
field, it will only have an effect if neither the Category nor the User Class have set a resource, as these will be given priority. In addition, the default resource is not preselected when creating new tickets, but only set after the ticket has been created.Checkbox
data type in particular, the default value can be used to control that only an activated checkbox should be accepted.