Card templates and custom fields
Use card templates in UQ Planner to give every task the same custom fields and starting description — priority, estimates, client, environment and more.
What a card template is
A card template is a named set of custom fields that a task can carry on top of the built-in ones — a bug's environment and steps to reproduce, a feature's estimate and client, a design task's Figma file. Templates belong to the organisation and can be used in any of its projects.
Create a template
- Open Templates in the sidebar (Owners and Admins can create and edit them).
- Choose Create Template and name it.
- Add fields. For each one set a name, a type, an optional description (shown under the field), a placeholder and a default value.
- Save. Edit it any time from the same page.
Field types
| Type | Use it for |
|---|---|
| Text | Short values: client name, environment, version, a URL. |
| Text Area | Longer text: acceptance criteria, steps to reproduce. |
| Number | Estimates, story points, budget hours. |
| Date | Release date, client deadline. |
| Boolean | Yes/no flags: “Needs design review”, “Customer-facing”. |
| File | A specific file the task needs, such as a brief or a mock-up. |
| Enum | Pick one from a list — enter the options one per line (e.g. Priority: Low, Medium, High). |
Organising fields into tabs
Every field sits on a tab — General by default. Give fields different tabs (for example Design, Implementation, Testing) and the task window shows them as tabs, so a long template stays readable. Use + Add to “tab” to add a field to a particular tab.
Use a template on tasks
- Per task: in a task's Template section pick the template; its fields appear below. “Default” means no template.
- Per project: set a Default Task Template on the project and every new task starts with it.
- From a parent: subtasks created from a task inherit its template.
Custom field values travel with the task everywhere — in update emails and in the Markdown the CLI downloads (under fields:), so an AI agent can read and set them too.
Template ideas
- Bug report: Environment (Enum), Version (Text), Steps to reproduce (Text Area), Customer-facing (Boolean).
- Client feature: Client (Text), Estimate (Number), Client deadline (Date), Approved by client (Boolean).
- Design to code: tabs Design (Figma link, Brief file) and Implementation (Estimate, Acceptance criteria).
Still stuck?
Email hello@uniqtech.dev with what you tried and, if it is about a task, its key (for example PRO-13). Pro organisations are answered first. Billing questions: see Contact.