Custom fields
Custom fields from your Jira site appear in the Column Picker automatically. Foundation detects each field’s type and gives it the right renderer and editor, so most custom fields are fully editable without any setup.
Add a custom field column
Section titled “Add a custom field column”- Open the Columns picker from the toolbar.
- Scroll to the custom fields section, or search by field name.
- Check the field — it appears as a new column.
See Add & hide columns for the full flow.
Supported field types
Section titled “Supported field types”| Field type | Renders as | Edit with |
|---|---|---|
| Single select | Lozenge | Dropdown of allowed values |
| Multi select | Multiple lozenges | Multi-select checklist |
| Radio buttons | Lozenge | Dropdown (same as single select) |
| Checkboxes | Comma-separated lozenges | Multi-select checklist |
| Cascading select | ”Parent / Child” text | Two-level dropdown |
| Text field | Plain text | Text input |
| Text area (rich text) | Extracted plain text | Read-only (edit in Jira) |
| URL | Clickable link | Text input with URL validation |
| Number | Right-aligned number | Number input |
| Date | Locale-formatted date | Calendar picker |
| Date-time | Locale date + time | Date-time input |
| User picker | Avatar + name | User search |
| Multi-user picker | Avatar chips | Search + add/remove |
| Group picker | Group name | Group search |
| Multi-group picker | Comma-separated names | Group search + add/remove |
| Version picker | Version name | Project-scoped version list |
| Multi-version picker | Version lozenges | Multi-select version list |
Edit a custom field
Section titled “Edit a custom field”The flow matches the matching system field:
- Click the cell.
- The appropriate editor opens — dropdown, picker, calendar, text box.
- Pick or type your value.
Enterto commit,Escto cancel.
For selects and pickers, Foundation fetches the allowed values directly from Jira for the specific issue you’re editing. So a “Region” select that has different options per project will show the right options each time.
Unsupported fields
Section titled “Unsupported fields”Jira has a huge ecosystem of custom field types, many from marketplace apps. When Foundation can’t safely edit a field, it does two things:
- Renders a best-effort display value — no
[object Object]glitches, no empty cells. - Makes the cell read-only — you can see the value, but you have to edit it in Jira.
Common read-only cases: rich-text (ADF) fields, Atlassian Teams, JSM-specific fields, Assets/Insight objects, and proprietary marketplace fields.