Custom fields
Every task comes with a set of built-in fields, and you can add your own on top. The built-in ones are system fields; the ones you create are custom fields. Together they let a task hold exactly the information your team needs — no more, no less.
System fields
Section titled “System fields”System fields are built into BridgeApp and appear on every task. You can fill them in and edit them, but you can’t create or delete them — they’re part of what a task is. They include:
- Assignee — who’s responsible
- Due date — when it’s expected
- Priority — how urgent it is
- Parent — the task this one is a subtask of
- Subtasks — the smaller tasks under this one
- Attachments — files on the task
- Relations — links to other tasks
- Task type — the kind of task it is
Because they’re universal, system fields work everywhere — you can filter, sort, and group by them in any view.
Custom fields
Section titled “Custom fields”Custom fields are fields you define to capture details specific to your work — a “Customer” name, an “Effort” estimate, an “Environment” dropdown, a “Cost” number. Each custom field has a name and a type (text, number, dropdown, and so on).
The key thing to understand: a custom field is bound to a task type, and it only appears on tasks of that type. So a “Steps to reproduce” field can live on Bug tasks without cluttering every Feature. This is what keeps each task focused on the details that matter for its kind of work.
| System fields | Custom fields | |
|---|---|---|
| Who creates them | Built in | You / your admins |
| Where they appear | Every task | Only tasks of the bound type |
| Can be deleted | No | Yes |
| Examples | Assignee, due date, priority | Customer, effort, severity |
Adding and editing custom fields
Section titled “Adding and editing custom fields”A project admin adds custom fields and binds them to a task type in the project’s settings. Once a field exists and is bound, it shows up in the task’s detail panel for every task of that type. Filling it in is as simple as typing in the box or choosing from the dropdown — changes save as you go.
Custom fields can have optional placeholder text — the faint hint shown in an empty field, like “e.g. Acme Corp.” It’s purely a visual nudge and doesn’t affect the value, filtering, or sorting.