Create a ticket form and required fields
Collect useful structured information without making every request carry the same questions.
- Permission to manage forms and a disposable test ticket.
Step-by-step walkthrough
- 01
Open Settings → Ticket forms & fields with a role allowed to manage form definitions. Review existing fields before creating another field with the same meaning.
- 02
Create fields with clear labels and appropriate types. Use choice values for a bounded set of answers, and explain what staff should enter when the label alone is not enough.
- 03
Create or edit a form and add the fields in a useful order. Review required fields and conditional requirements so they match the intended ticket workflow.
- 04
Use Edit & preview to check the form. Exercise each condition with a test ticket, including the case where a required answer is missing.
- 05
Apply the form to an appropriate ticket and save its values. Verify the saved information survives reopening the ticket before making the form part of routine intake.
A closer look at the interface
These are actual product captures from a fictional demo workspace. Navigation and available controls can differ by role, configuration, or release.
Ticket forms and fields
- 1Switch between Forms and Fields.
- 2Edit and preview before applying a form.
- 3Archive definitions when they should leave active use.
Expected result
A tested form that collects the right information at the right point in the workflow.
Important details
Archiving a definition is different from deleting historical ticket values. Review existing usage before changing a form.
Need help with this workflow? Contact the team and include this guide’s title.