Custom Fields
Capture structured data alongside every feedback post — ARR, urgency, account IDs, anything specific to how your team triages — without forcing it into the title or description.
What Is a Custom Field?
Custom fields let you attach structured data to feedback posts. While categories and tags are great for navigation and filtering, custom fields are where you store the values that matter to your triage process — things like:
- A customer's ARR (number)
- Urgency level (Low / Medium / High)
- Account ID (text)
- Source meeting date (date)
- Linked Jira ticket key (text)
Custom fields are managed per feedback board, but every field you create joins an organization-wide pool — so a field defined on one board can be reused on any other via Add From Existing. Custom fields are available on feedback boards only; roadmap boards don't have them.
Supported Field Types
| Type | Description | Example Use |
|---|---|---|
| Text | Single-line free text | Account ID, Linked ticket |
| Multiline Text | Multi-line free text | Internal notes, Acceptance criteria |
| Number | Numeric input | ARR, Effort estimate |
| Dropdown | Single-choice picker from a defined list | Urgency, Region |
| Multiselect | Multiple choices from a defined list | Affected products, Personas |
| Date | Date picker | Target ship date, Customer renewal |
| Checkbox | Single on/off toggle | Has SLA, Internal use only |
Create a Custom Field
Custom fields live inside the feedback board form — there's no separate Custom Fields settings tab.
Open the board
Go to Settings → Feedback and open the feedback board you want the field on.
Find Customize post input fields
Scroll to the Customize post input fields section of the board form and click Add new custom field.
Configure the field
In the Create Custom Field modal, set:
- Field type — Text, Multiline Text, Number, Dropdown, Multiselect, Date, or Checkbox
- Label — what appears on the post form (e.g., "Customer ARR")
- Placeholder (optional) — helper text shown in the input
- Mark as optional field — checked by default; uncheck to make the field required
- Options (Dropdown & Multiselect only) — define the choices users can pick from, and drag to reorder them
Reuse fields across boards
To add a field that already exists on another board, click Add From Existing and search the organization-wide pool instead of creating a duplicate.
Reorder
Drag fields within the board form to control the order they appear on that board's post form.
Deleting a custom field removes it from all boards that use it, and can't be undone.
When to Use Custom Fields vs. Tags vs. Categories
| Use | Best For |
|---|---|
| Custom Field | A specific value per post (number, date, single choice from a long list) |
| Tag | Many free-form labels per post for filtering |
| Category | One broad theme per post (Bug, Idea, Question) |
If you find yourself making a tag for every possible value of something (e.g., tags like "ARR-10k", "ARR-50k", "ARR-100k"), you want a custom field instead.
Custom fields capture data on the post form, but they aren't filterable — inbox filters, saved views, and user segments don't support custom-field conditions. If you need to slice posts by a value, consider whether a tag fits better.
Setting Field Values
Custom fields appear on the post submission form of every board they're added to — whoever creates the post (on the portal, in the widget, or from the dashboard) fills them in.
Best Practices
Start with two or three fields that drive real decisions. It's tempting to add a custom field for every "wouldn't it be nice to track" — but every required field is friction on the form. Keep the public-facing form short.
- Make most fields optional. Required fields slow down submission. Uncheck Mark as optional field only if you genuinely can't process the post without the value.
- Use Dropdown for known sets. If the value is one of a small fixed list (Urgency, Region, Persona), use Dropdown — it forces consistency.
- Use Number for quantities. ARR, effort estimate — these are far more useful as numbers than as text.
- Don't put PII in custom fields. Fields appear on the public post form, so treat them like any public form input.