Ticket fields

Every field type, when to use each, and how Required, help text and requester visibility make better tickets.

Fields are the questions you ask about every ticket. Good fields mean nobody has to call back to ask "which store?" or "how much did it cost?"

Every ticket already has a title, an owner, a due date, comments and files, so you don't need fields for those.

Field types

Type	Use it for
Text	Short answers: a model number, a room
Text with formatting	Longer descriptions with bold, lists and links
Number / Currency	Quantities and costs; reports can total them
Date	Anything with a date besides the due date, like "delivered on"
Email, Phone, URL	Contact details; they become clickable
Choose one / Choose any	A dropdown or a set of checkboxes from your own list
Checkbox	Yes/no, like "Warranty?"
Checklist	A list to tick off on the ticket, like an opening or inspection list. See Checklists and signatures
Person	Someone in your company, like "Approved by"
Location	One of your company's locations
Team	One of your company's teams
Attachments	Photos, PDFs and other files
Signature	Someone signs on the ticket with a finger or mouse, like at pick-up
Horizontal bar / Text box	A divider that splits a long form into parts, or a few lines of instructions

To reorder fields, drag one on the ticket preview: the one you're holding fades, and a line shows where it will land. The ↑ ↓ buttons work too.

Required. The ticket can't be created without it. Use it for what you truly can't work without; too many required fields and people give up.
Help text. A short hint under the label, like "Front of house or kitchen?" It's the cheapest way to get better answers.
Width. Third, Half or Full: three thirds or two halves share a row, which keeps forms short. On a phone every field takes the full row.
Default value. What new tickets start with, like your main store in a Location field or Normal in Priority. People can change it. It also fills in tickets that arrive without it (a web form that hides the field, email, schedules or the API); imports keep what the spreadsheet had. A date can default to The day it's made, to a while after (like in 2 weeks), or to a set date.
Private. New fields show to requesters (on the web form and their page for the request). Turn on Private for internal fields, like cost or vendor, that the person asking shouldn't see.
On a phone, the ticket comes first: tap + Add a field for the field library, tap a field for its options, and use ↑ ↓ and 🗑 to reorder and remove.
Removing a field. Hover a field on the preview and click 🗑, or drag it back onto the Add fields panel. Rules, automatic actions and emails that used it are removed with it. See What requesters see.

A field can be required only at a certain step, like "Cost" before closing. That's a step rule.
A step can fill in a field for you. See Automatic actions.
On the web form, any field can be shown, pre-filled, hidden with a fixed value, or filled from the link.

Still stuck? Email hello@ticketstacker.com. A real person reads every message.