feat: Allow users to define custom states

[ccachoulet]

Problem Statement

Currently, Kaneo enforces a set of predefined states for tracking items. This forces teams to adapt their internal workflows to Kaneo’s model, which can create friction and reduce flexibility. For example: we need to adapt our processes to fit the tool, instead of the tool adapting to our processes.

Proposed Solution

Allow the creation and management of custom states. Users could define their own states (with a label, a color, and optionally a description). These custom states would integrate seamlessly into the existing workflow (transitions, filters, views, etc.).

Alternative Solutions

Map our internal processes to the default states, but this is limiting and requires compromises. Use tags or labels, but this doesn’t provide true step-by-step tracking. Relevant Context

Example: in our organization, we have specific steps ("Pending validation from X", "Client review", "Blocked by external dependency") that cannot be represented with the default states.

Other tools (e.g., Jira, Linear) allow configuring custom states, which makes them much more adaptable to diverse workflows.

Does this feature align with Kaneo's focus on simplicity?

Yes, because the ability to customize states makes Kaneo more flexible without adding complexity for teams that are fine with the defaults. Each team can keep a simple workflow adapted to their context, instead of being forced into a one-size-fits-all model.

[usekaneo[bot]]

🎯 Task created - feat: Allow users to define custom states

Task Details

• Task ID: andxcgzt89ljx327ju1qhu7t
• Priority: medium
• Status: to-do

This issue is automatically synchronized with your Kaneo project.

[Heart1010]

+1 for that

[aacevski]

Hey, I'm mostly going to tackle this for the version 2 of Kaneo which should be released very soon. (The beta is already out on our Discord server!)

Keeping this open until I complete it in the v2 branch.