feat: Allow sharing board configurations across projects

[ccachoulet]

Problem Statement

In Kaneo, we can create boards, and a feature for custom states has already been validated. However, once these custom configurations are available, there will still be a limitation: each project will need to be configured manually. If teams have detailed or standardized setups, it would be inefficient to recreate the same configuration (states, columns, rules, etc.) for every new project.

Proposed Solution

Add a feature to share or replicate board configurations across different projects.

For example:

• Allow users to export/import a board configuration.
• Or enable them to use an existing board as a template when creating a new one.

This would make the upcoming custom states feature much more powerful by ensuring consistency and saving setup time.

Alternative Solutions

• Introduce a board template system that can be saved and reused.
• Allow duplication of boards between projects, not only within the same project.
• Provide an API endpoint for importing/exporting configurations to automate the process.

Relevant Context

This request builds upon the previously approved feature for custom states. To make it truly efficient for teams working across multiple projects, the ability to share or duplicate configurations will be essential. For example, if a team has defined detailed workflows (e.g., Design, Review, QA, Blocked), they shouldn’t have to manually recreate them each time.

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

Yes, because it simplifies project setup and ensures consistent workflows across projects. It enhances productivity while keeping the overall Kaneo experience simple and streamlined.

[usekaneo[bot]]

🎯 Task created - feat: Allow sharing board configurations across projects

Task Details

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

This issue is automatically synchronized with your Kaneo project.

[aacevski]

Makes sense, I think I will add this right away with the custom statuses.

[ccachoulet]

I think I realize this personally when I use boards; it saves a huge amount of time not having to reconfigure the workflow for each project.