github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-06 11:37:49 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

[Feature Request] Ability to define or save a "Default Kanban View" for new projects #2464

New Issue
Open
opened 2026-03-22 14:08:25 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-03-22 14:08:25 -05:00
Owner
Copy Link

Originally created by @Kuphi on GitHub (Jan 5, 2026).

Ability to define or save a "Default Kanban View" for new projects

Is your feature request related to a problem? Please describe:
Currently, all new Kanban projects default to three hardcoded buckets: "To-Do", "Doing", and "Done". Many users have specific workflows (e.g., "Backlog", "In Progress", "Testing", "Released") and must manually rename or recreate buckets every time a new project is started.

Describe the solution you'd like:
I would like a way to set a global or per-user "Default Kanban Template." Specifically:

An option in the Project View settings (the three dots) labeled "Set this view as default for new projects." When clicked, any future project created with a Kanban view would automatically inherit the bucket names.

Additional context:
This could be implemented as a simple toggle in the project_views table or as a user-level configuration setting. It would significantly reduce friction for users who manage many small projects.

Which alternatives did you consider using instead?

Duplicating a "Template Project": This works but is a manual "opt-in" process rather than a system-wide setting.

Modifying source code: Not viable for users which don't compile from source code or those who want to stay on the main update branch.

Originally created by @Kuphi on GitHub (Jan 5, 2026). ### Ability to define or save a "Default Kanban View" for new projects **Is your feature request related to a problem? Please describe:** Currently, all new Kanban projects default to three hardcoded buckets: "To-Do", "Doing", and "Done". Many users have specific workflows (e.g., "Backlog", "In Progress", "Testing", "Released") and must manually rename or recreate buckets every time a new project is started. **Describe the solution you'd like:** I would like a way to set a global or per-user "Default Kanban Template." Specifically: An option in the Project View settings (the three dots) labeled "Set this view as default for new projects." When clicked, any future project created with a Kanban view would automatically inherit the bucket names. **Additional context:** This could be implemented as a simple toggle in the project_views table or as a user-level configuration setting. It would significantly reduce friction for users who manage many small projects. ### Which alternatives did you consider using instead? Duplicating a "Template Project": This works but is a manual "opt-in" process rather than a system-wide setting. Modifying source code: Not viable for users which don't compile from source code or those who want to stay on the main update branch.
GiteaMirror commented 2026-03-22 14:08:26 -05:00
Author
Owner
Copy Link

@wucherpfennig commented on GitHub (Mar 13, 2026):

I would like to second this issue too.

a config setting would be handy

@wucherpfennig commented on GitHub (Mar 13, 2026): I would like to second this issue too. a config setting would be handy
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#2464
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?