The Form Library — Managing and Assigning Forms to Categories

This guide covers managing your form library: how to organise published and draft forms, how to assign a form to a ticket category or board, and how versioning protects existing answers.

The form library

The Form Library is the central list of all forms in your organisation. Each entry shows the form name, its current status (draft or published), and how many places it is assigned to.

From the library you can:

• Open the builder — edit fields, labels, options, and structure
• Duplicate — create a copy as the starting point for a new form
• View version history — see all published versions and when each was created
• Archive — remove a form from active use. Archived forms won't appear in assignment pickers, but existing ticket answers remain readable

Assigning a form to a category

The most common assignment is to a ticket category. When a form is assigned to a category, every ticket created in that category will show the form fields inline in the creation window.

To assign from the library: open the form, go to Assignments, and click Add assignment → Category. Pick the board, then pick the category within that board.

To assign from Board Settings: go to Board Settings → Categories, edit a category, and select a form from the dropdown that appears.

One category can have one active form at a time. When the form is updated, the category automatically uses the latest published version for new tickets from that point on.

Assigning a form to a board

A board-level assignment shows the form on every ticket created on that board, regardless of category. This is useful for boards where all incoming tickets need the same information — for example, a board that only handles one type of work.

Category-level assignments take priority over board-level ones. If a ticket's category has its own form, that form shows instead of the board-level form.

Removing an assignment

Open the form's Assignments tab (or the category/board settings) and remove the link. Existing tickets are not affected — their captured answers remain visible. Only new tickets will stop showing the form.

How versioning protects old answers

When you publish an updated version of a form, tickets created before the update retain their answers displayed against the original version. The new version applies to tickets created after the update. This means you can freely improve forms over time without changing the record of what was originally submitted.

The version history in the library shows a timeline of all published versions, the date each was published, and a count of how many tickets were created under each version.