Field Types

Overview

Fields determine what information a ticket captures. When you build a form, you choose which fields it includes.

Every field has a category — predefined, custom or shared — and a field type that defines what it captures. This article explains both.

To learn about forms and how they relate to tickets, read more in Forms. To build a form and add fields, see Create & Edit Forms.

Field Categories

Fields fall into three categories, by how they are created and shared:

	Predefined	Custom	Shared
Created by	PlanRadar	You, on a form	You, at account level
Field type	Fixed, with special functionality	Any field type	Any field type
Shared across forms	Yes	No	Yes
In filters and reports	One entry across forms	One entry per form	One entry across forms

Predefined Fields

PlanRadar offers a number of predefined fields with specific functionalities:

Title: This field allows you to provide a short but descriptive title for the ticket, summarising its main purpose or issue.
Assignee: Use this field to assign the ticket to a specific person or group who will be responsible for dealing with it.
Read more in Set the Assignee & Receivers of a Ticket.
Receiver (CC): Set receivers to keep users informed of activity on the ticket.
Read more in Set the Assignee & Receivers of a Ticket.
Due date: Use Due dates and Extension dates to stay ahead of deadlines.
Read more in Set a Due Date or Extension Date for a Ticket.
Status: This field reflects the current stage of the ticket, providing an overview of its progress. Available statuses are: Open, In Progress, Resolved, Feedback, Closed, and Rejected.
Read more in Set Status & Progress of a Ticket.
Priority: This field allows you to categorise a ticket based on its urgency or importance. It helps to determine the order in which tickets should be addressed.
Progress: Use Progress to track the percentage of a ticket's completion.
Read more in Set Status & Progress of a Ticket.
Parent Ticket: Define the parent of a sub-ticket.
Read more in Use Sub-Tickets.

Predefined fields have fixed names and values; for example, the Status field has a predefined list of statuses. However, you are free to choose whether to include these fields in your form and the order in which they appear. Only the title field is mandatory and automatically added to new forms.

Custom Fields

Custom fields are fields you create on a form to capture your own information. You choose a field type (see Field Types below), and the field belongs to the form you create it on.

To use the same custom field on several forms, create a shared field instead.

Shared Fields

Shared fields let you define a field once at account level and use it across any number of forms, instead of recreating the same field on each form. They support the same field types as custom fields.

A shared field works on two levels:

The shared definition — its name, field type and list — is set once at account level and is the same on every form. It is shown but cannot be changed on a form.
Per-form settings — such as whether the field is mandatory, its default value, order, visibility and permissions — are set on each form. Some, such as whether the field is mandatory, can be adjusted again per project when the form is assigned to a project.

Because a shared field is one field across all forms, it appears once in the ticket filters (under Predefined and shared fields) and as a single column in reports and exports — the same way predefined fields do. A custom field, by contrast, appears once per form.

Read more in Create & Manage Shared Fields.

When you create a custom or shared field, you choose a field type that defines what it captures.

Text

Short text is limited to one line; long text can have multiple lines. Use text fields to capture detailed information or descriptive comments.

Number

Use a Number field for whole numbers, such as quantities or measurements. Use a Decimal field for values with a decimal separator (for example, 1.5 or 1,5, depending on locale).

Date and Time

Use a Date field for a specific date, and a Time field for a time in hours and minutes.

Checkbox

Use a Checkbox when users should check or uncheck an option.

List

A List field lets users choose from a predefined set of values, which keeps data consistent and speeds up entry. A list field can also allow multiple selections. List items can be structured in a hierarchy of up to 10 levels of items and sub-items. Read more in Lists.

User Field

Custom user fields provide additional flexibility for complex use cases. Use them instead or in addition to the default assignee and receiver fields. You can:

add multiple custom user fields to a form with custom titles.
allow single or multi-selection of users in the project.

Depending on the user's notification settings, they can receive notifications the same way as assignees and receivers. Read more in Configure E-Mail Notifications.

Like all other fields, you can filter by field values in the ticket views and include them in ticket reports. Currently user groups are not supported in the user field. Read receipts of tickets only consider the assignee field, not custom user fields.

Attachment Field

The Attachment field allows users to attach files and photos directly to a specific field. For example, you can capture before-and-after photos in separate fields. This works in addition to General attachments, which are attached to the ticket as a whole rather than to a specific field.

General attachments and field attachments are added and viewed separately.
Read more in Add Attachments to Tickets and in View Ticket Attachments.
Subcontractors can upload attachments to fields. The Attachment field is the only custom field for which PlanRadar allows you to grant editing permissions to users with the free subcontractor user type. This permission also allows users to delete any attachment in that field.
Read more in Edit Field Permissions.
Each form can contain multiple attachment fields, each with its own name and description.
Read more in Create & Edit Forms.
Each attachment field can have up to 50 files attached by default. The file limit can be reduced for each field.
Read more in Edit Field Properties.
Ticket filters such as Has photos or Has attachments include both general attachments and attachments from all fields.
Read more in Filter Tickets.
Additional ticket filters allow filtering specifically for tickets that have attachments in a selected attachment field.
Supported file types are the same as for general ticket attachments:
- Supported document file types: pdf, xls, xlsx, ods, csv, doc, docx, odt, dwg, dxf, eml, msg
- Supported image file types: jpg, png, gif, heic
- Supported archive file types: zip, rar
- New photos and videos are usually captured and uploaded via the mobile app.
- Audio recordings are supported for general ticket attachments only.
In Basic ticket reports (PDF and Excel), all images and documents are included, regardless of whether they are attached to the ticket or to a field.
Read more in Create Basic Ticket Report Templates and in Create Excel Templates for Exporting Tickets.
For Advanced ticket reports, you can define in the template builder where attachments from each field should appear, using the same options available for general ticket attachments.
Read more in Create Advanced Ticket Report Templates.

Checklist Field

The Checklist field lets users record a response from a configurable set of predefined options — useful for inspections, quality checks, and compliance workflows.

Select one of the three sets of response options per checklist field:

Yes / No / N/A
True / False / N/A
Pass / Fail / N/A

Select one of the three sets of response colours per checklist field:

Green / Red / Blue
Red / Green / Blue
Blue for all

Additional field properties:

Attachments — enable attachments to allow users to add attachments. Attachments for checklist fields work the same way as for the Attachment Field — read more above.
Notes — enable notes to let users add a note alongside their response.
Mandatory settings — you can make the selection of a response mandatory and/or make adding a note and/or an attachment mandatory depending on the selected response(s) e.g. attachment required when response is "No" or note required for any response.
Conditional visibility — a checklist response can be used as the trigger condition for showing or hiding other fields. Read more in Define Conditions to Show/Hide Fields.
Filtering — checklist fields appear as custom field filter criteria, grouped by form. You can filter by one or more response options (e.g. all tickets with a Fail response) or for tickets where the field has no value. General filters such as Has attachments, Has images, Has documents, and Has videos include attachments from checklist fields. Filtering specifically for attachments or notes within a checklist field is not yet possible. Read more in Filter Tickets.