Ticket layouts in the project settings
On this page you define which fields appear on a ticket's detail view, and which ticket types this layout is assigned to.
You find this page in project settings under the "Ticket layouts" tab. Ticket layouts are a Pro feature and are only available in projects with a Pro or Enterprise subscription.
Who can see and edit this page
The overview is visible to everyone with access to project settings. Creating, editing and deleting require the "change project ticket layouts" write permission - by default, only the Project Manager role has this right.
Overview table
The table shows: the layout's name, creator, creation date, assigned ticket types, the fields it contains (as a list), and the number of tickets currently using this layout. Most columns are sortable; the field-list column is not. This overview table has fixed, hard-coded columns — there is no column-settings menu to show/hide columns here.
Creating a new layout
The round plus button in the bottom right opens a menu with three options: create a new layout from scratch, copy a layout from another project in your company, or copy a layout from company settings (if your company has defined any there). When copying, the ticket-type assignment is always cleared — you need to set it again afterwards.
Editing a layout: the field builder
The edit dialog isn't a classic form, but a two-column builder: a palette of available fields on the left, your current layout on the right. Two fields are always included and cannot be removed: title and ticket type. Every change — a new layout, changed fields, changed type assignment — is distributed to all project members immediately. If someone opens a ticket of an affected type, they immediately see the updated layout.
Adding a field: drag a field from the left palette into the drop zone on the right (on small screens, via a "+ field" button). For custom field types, a type-specific options dialog opens immediately, where you set the label, required status, default value and other settings.
Editing or deleting a field: via the "⋮" menu on each field.
Reordering: drag the handle icon on each row.
Available field types at a glance
System fields – fixed, system-defined ticket properties:
Status – shows/sets the ticket's status (e.g. open, in progress).
Description – multi-line free text field for the ticket description.
Plan – shows which plan the ticket is pinned to, or lets you assign one.
Due date – date by which the ticket should be completed.
Assignee – the person responsible for working on the ticket.
Approver – the person who should sign off/approve the ticket once it's done.
Tags – multi-select from the tags defined in the project.
Craft – assignment to one of the crafts (trades) defined in the project.
Time tracking – enables recording time on the ticket.
Custom field types – freely configurable additional fields that you name yourself:
Number – a numeric value, e.g. with a unit, minimum/maximum, and decimal places.
Text – a single-line or multi-line free text field.
Date – selection of a single calendar date.
Date range – selection of a period with a start and end date.
List – selection of exactly one value from a list of values you define; can be the basis for conditionally visible rule fields.
Multi-select list – like list, but with several values selectable at once.
Checkbox list – several checkboxes that can be ticked independently of each other.
Person – selection of exactly one person (e.g. a project member or contact).
Multi-person – selection of several people at once.
Divider – a purely visual element to structure the layout, with no value of its own.
Progress – shows/records a completion percentage.
Creating and using rules on list fields
For fields of type list or multi-select list, you can create "rules": additional fields that are only shown on the ticket when specific values are selected in the list.
Creating a rule: open the "⋮" menu of the list field and choose "Add rule". A new, empty rule block appears directly below the field.
Setting trigger values: use chips to select one or more values from the list that should trigger the rule. If any one of the selected values is set on the ticket, the rule becomes active — you don't need all selected values at once, one is enough.
Adding fields to the rule: the rule block has its own drop zone — you add fields the same way as in the rest of the layout, via drag & drop or the "+ field" button. A rule can contain several fields. A rule field can itself be of type list, but you can't create a further, separate rule inside a rule — only one level of nesting is possible.
Behavior on the ticket: when someone selects one of the trigger values on the ticket, the app automatically shows the rule's fields; selecting a different value hides them again. Values already entered in the rule's fields are not lost — they stay saved on the ticket and reappear as soon as the matching trigger value is selected again.
Editing or deleting a rule: change trigger values directly via the chip selection; edit or delete individual fields within the rule via their own "⋮" menu. Remove the entire rule via the "X" next to the value selection, with a confirmation prompt.
Saving: a rule must have at least one trigger value and at least one field — if either is missing, the app warns you and saving the layout is blocked.
Preview: a button shows you a live preview of a ticket with this layout, including the showing/hiding of rule fields.
Assigning ticket types
The ticket icon on a table row opens a multi-select of all ticket types available in the project (you can't create new types here — that happens in the "Types" tab). A ticket type can only ever be assigned to one layout at a time — assigning it to this layout automatically removes it from any other layout that previously contained it. If the change affects types already in use, a warning listing the affected type names appears first and requires your confirmation.
Important effect when removing a field: real data loss
Removing a field from a layout doesn't just hide it — for existing tickets that already have data stored in that field, this data is actually deleted. Before that happens, the app shows you a warning with the affected field names and requires explicit confirmation ("Delete"). If you cancel, the layout stays unchanged. This deletion cannot be undone afterwards (other than manually re-entering the values on the tickets).
Deleting a layout
The trash icon lets you delete an entire layout. If at least one ticket is assigned to one of this layout's assigned ticket types, deletion is refused — with no way to force it. Remove the type assignment or change the affected tickets first before deleting the layout.
Was this article helpful?
No upmesh account yet?
Try upmesh for free: construction documentation, defects, plans and site diary in one app — in the browser, on your phone and offline.