Custom fields are the foundation of TskVlo’s flexibility. Every board starts with a Name field and a Status field, but you can add as many fields as your workflow requires. This guide covers all 12 built-in field types, when to use each, and how to configure them.
Adding and Managing Fields
To add a field to a board, click + Add Field in the table header row, or go to Board Settings → Fields → Add Field. You’ll see a menu of all available field types.
To edit or delete a field, hover over the field name in the header and click the settings icon. Field changes apply immediately to all items on the board.
TEXT
When to use it: Free-form text notes, descriptions, short labels, or any unstructured data that doesn’t fit a specific type.
Configuration options:
- Single-line (default) — shows as a compact input
- Multi-line — expands to a text area for longer content
Example use cases:
- “Notes” field on a bug tracker for reproduction steps
- “Client Contact” on an account management board
- “Short Description” for a content calendar
Tip: For rich text with formatting, use the built-in item description editor instead of a text field.
NUMBER
When to use it: Integers, decimals, counts, money amounts, story points, or any quantitative value.
Configuration options:
- Decimal places (0 for integers, 1–4 for decimals)
- Prefix/suffix (e.g., ”$”, ”€”, “pts”, “h”)
- Minimum and maximum value constraints
Example use cases:
- “Story Points” on a sprint board
- “Budget (€)” on a project board
- “Hourly Rate” on a client work tracker
STATUS
When to use it: Workflow stages, approval states, priority levels, or any field where items must be in exactly one of a defined set of states.
Configuration options:
- Add, remove, and reorder status options
- Assign a color to each option
- Set a default value for new items
Example use cases:
- “Priority” with values: Low (gray), Medium (blue), High (orange), Critical (red)
- “Approval Status” with values: Pending, Approved, Rejected
- “Stage” with values: Concept, Design, Development, QA, Done
Tip: Every board has a built-in Status field, but you can add additional Status fields for independent dimensions (e.g., both a workflow status and a priority status).
DATE
When to use it: Single-point-in-time dates like deadlines, publish dates, or event dates.
Configuration options:
- Date format (ISO, European, US)
- Include time (for scheduling down to the hour)
Example use cases:
- “Due Date” on any task board
- “Publish Date” on a content calendar
- “Interview Date” on a hiring tracker
DATE_RANGE
When to use it: Periods with a defined start and end, like project phases, campaigns, or availability windows.
Configuration options:
- Date format
- Include time
Example use cases:
- “Campaign Period” on a marketing board (e.g., “Jun 1 – Jun 30”)
- “Sprint Dates” on a development board
- “Event Duration” on an event planning board
PERSON
When to use it: Assigning responsibility, tracking authorship, or linking items to workspace members.
Configuration options:
- Single assignee (default) — only one person can be assigned
- Multiple assignees — useful for co-ownership or review chains
Example use cases:
- “Assignee” on any task board
- “Reviewer” on a content approval workflow
- “Account Manager” on a CRM-style board
Note: The dropdown shows only active workspace members. Invite team members via Workspace Settings before using this field.
CHECKBOX
When to use it: Simple boolean flags — true/false, yes/no, done/not done.
Configuration options:
- Label for the checked and unchecked state (optional)
Example use cases:
- “Billable?” on a time tracking board
- “Client Approved?” on a deliverables tracker
- “Automated Tests Passing?” on a release checklist
TAGS
When to use it: Categorization with multiple values per item, where an item can belong to several categories simultaneously.
Configuration options:
- Define the set of available tags (or allow free-form entry)
- Reuse existing board tags from inline suggestions while editing
Example use cases:
- “Labels” on a bug tracker (frontend, backend, UX, performance)
- “Channel” on a content calendar (Blog, Twitter, LinkedIn, Email)
- “Technology” on a project board (React, Node.js, PostgreSQL)
Tip: Tags are different from Status — an item can have multiple tags but only one status value per Status field. Tag chips use a shared color palette across editing, display, and shared board views — shown in the same soft-background, colored-text style as Status chips and tuned for both light and dark mode — and TskVlo suggests existing tags from the same board field so teams can reuse labels consistently.
URL
When to use it: Web links that should be displayed as clickable links rather than plain text.
Configuration options:
- Display text (show the URL itself or a custom label)
Example use cases:
- “Design Mockup” linking to a Figma file
- “Staging URL” linking to the test deployment
- “Reference” linking to a spec or document
RATING
When to use it: Subjective quality scores, priority ratings, or satisfaction levels on a 1–5 star scale.
Configuration options: None beyond the label — ratings always use a 1–5 star scale.
Example use cases:
- “Complexity” on a feature backlog (1–5 stars)
- “Client Satisfaction” on a project retrospective board
- “Business Value” for product prioritization
PROGRESS
When to use it: Visual progress tracking for tasks that have measurable completion percentages.
Configuration options:
- Minimum value (default 0)
- Maximum value (default 100)
- Display as percentage or raw number
Example use cases:
- “Completion %” on project milestones
- “Budget Used” as a progress bar showing spent vs. total
- “Onboarding Progress” for a new hire checklist
FORMULA
When to use it: Values that should be calculated automatically from two Number fields instead of entered by hand.
Configuration options:
- The two Number fields to use as inputs
- Operation: sum, difference, product, or quotient
Example use cases:
- “Total Cost” computed as Hourly Rate × Estimated Hours
- “Remaining Budget” computed as Budget − Spent
- “Cost per Unit” computed as Total Cost ÷ Quantity
Common Field Settings
Every field, regardless of type, has a name, an optional description, a display width, a required flag, and a hidden flag. Required fields are enforced — an item can’t save field values until every required field has a value.
Looking for file attachments? Files aren’t a field type — attach documents, images, or PDFs (50 MB per file by default) directly to items and comments instead.
Looking for cross-board links? A dedicated Relation field type is on the roadmap. For blocking relationships today, use the built-in item dependencies (see the Relations guide).
Field Display Order
Fields appear in the order you add them. In Table view, you can drag columns to reorder them. Use Board Settings → Fields to hide or show fields per view — this is useful for keeping the table focused without permanently deleting fields.
Field Limits
There’s no hard limit on the number of fields per board, but for readability we recommend keeping it to 10–15 actively visible fields. Use field visibility settings to show only what’s relevant per view.