Custom fields

Adding a new custom field

All Custom Fields

Custom fields allow you to tailor issue forms to your operational or reporting needs. Below is an overview of each field type and its configuration options.

Adding a Field

Configuration of a Text Field
Configuration of a Text field

You can add a new field by clicking the “Add Field” button.

  • Unnamed field – The text you type here becomes the field label visible in the issue form.

  • Help text – Add contextual guidance for users. This helps explain what kind of input or data is expected. Example: “Enter the batch ID as printed on the product label.”

  • Mandatory – Choose whether a field is required. If enabled, users must fill it in before submitting the issue.

  • Remove – Click the trash can icon to remove a field from the form.

  • Field details – You can collapse or expand field details during configuration using the arrow next to the field name.

  • Sequence – Change the order of fields by dragging and dropping them.

  • Collapse & expand fields – For better overview, you can collapse or expand all fields simultaneously.


Text Field

Use: Allows free text input in an issue.

Examples:

  • Describe an incident or observation.

  • Add operator notes or comments.

  • Enter identifiers like “Shift A” or “Lot 42”.


Number Field

Use: Allows numeric input in an issue.

Examples:

  • Enter quantities (e.g., number of defective items).

  • Record measurements (e.g., temperature = 72°C).

  • Count cycles, incidents, or hours worked.


Choice Field

Use: Allows users to select from predefined options.

Extending the Selection

  • Add options – Click the plus icon to add new choices.

  • Remove options – Click the trash icon to delete an option.

Possible Configurations

  • Dropdown – Options appear only when the list is opened. Saves space and can allow either single or multiple selections.

  • Radio buttons – All options are visible, but only one can be selected.

  • Checkboxes – All options are visible, and multiple selections are allowed.

Examples:

  • Status: Open / In Progress / Closed

  • Priority: Low / Medium / High

  • Department: Production / Maintenance / Quality


Data Field

Use: Reuses existing lists for consistent and structured data.

Configuration

  • Single – Select one item from the list.

  • Multi – Select multiple items if applicable.

Possible Lists

  • Equipment – Shows all available machines. Example: “Packaging Line 3” or “Mixer 1”.

  • User – Displays all active users. Example: Assign an issue to “John Doe (Operator)”.

  • SKU – Lists all available Stock Keeping Units (SKUs). Example: “SKU-4589 | Vanilla Yogurt 500g”.

Examples:

  • Selecting the responsible operator for an issue.

  • Linking the issue to a specific SKU or machine.

  • Choosing multiple machines for a maintenance report.


Date & Time Field

Use: Allows users to input or select a date and/or time.

Examples:

  • Date of inspection: 2025-11-05

  • Downtime start: 14:32

  • Expected completion: 16:00


File Upload Field

Use: Allows uploading one or more files when creating or editing an issue.

Examples:

  • Upload a picture of a damaged component.

  • Attach a PDF of a maintenance report.

  • Add screenshots or supporting documents for analysis.


Tip: Combine multiple field types (e.g., a text field for comments + a data field for machine ID) to create structured, yet flexible issue forms.

Last updated