Hi everyone,
I’d like to propose adding support for custom fields in Vikunja. Currently, tasks are limited to the built-in attributes (priority, due date, labels, assignees, etc.), which works well for general task management but falls short for teams that need to track domain-specific data.
Use case examples:
**•** A recruiting team tracking “Candidate Source” or “Interview Stage”
**•** A content team tracking “Word Count” or “Publish Channel”
**•** A support team tracking “Ticket Severity” or “Customer ID”
Proposed functionality:
**•** Field types: text, number, date, dropdown/select (single or multi), checkbox, URL
**•** Fields definable at the project level, so different projects can have different custom fields
**•** Custom fields visible and editable in the task detail view
**•** Custom fields available as columns in the table/list view
**•** Filterable and sortable, same as native fields
**•** Optional: expose via API for integrations
Why this matters:
Many competing tools (Asana, ClickUp, Notion) offer this, and it’s often cited as a blocker for teams migrating to Vikunja from those platforms. It would meaningfully increase Vikunja’s flexibility for specialized workflows without touching its clean core design — as long as custom fields stay optional and off by default.
Open questions for discussion
**•** Should custom fields be scoped per-project or globally reusable across projects?
**•** Should there be a field limit for performance/DB reasons?
**•** Priority: is this better suited as a core feature or a plugin/extension once Vikunja has an extension system?
Curious to hear whether this has been discussed before, and what the maintainers think about feasibility given the current data model.