Kanban Feature Request: Have a Default Project/Kanban Board be Shown #6962

Open
opened 2025-11-02 07:12:13 -06:00 by GiteaMirror · 4 comments
Owner

Originally created by @zaha on GitHub (Mar 3, 2021).

In most cases I only need a single project/kanban board per repository. I would like to set a kanban board as the default which

  • will then be immediately shown when I click on the "Projects" tab
  • will be automatically set as the project on any new issues

Right now I have to click "Projects", look for the single board and then click it again, which adds up a lot of unnecessary clicks over time.
Same when creating issues, requiring two additional clicks to add the issue to the board. I can also see this made more comfortable by having this be done by #14824 (new issue button on Kanban Board) alternatively.

Originally created by @zaha on GitHub (Mar 3, 2021). In most cases I only need a single project/kanban board per repository. I would like to set a kanban board as the default which - will then be immediately shown when I click on the "Projects" tab - will be automatically set as the project on any new issues Right now I have to click "Projects", look for the single board and then click it again, which adds up a lot of unnecessary clicks over time. Same when creating issues, requiring two additional clicks to add the issue to the board. I can also see this made more comfortable by having this be done by #14824 (new issue button on Kanban Board) alternatively.
GiteaMirror added the topic/projectstype/proposal labels 2025-11-02 07:12:13 -06:00
Author
Owner

@delvh commented on GitHub (Mar 5, 2021):

Well, I can understand your request, but there are two sides to that feature:

  1. Those that use a single project for all issues or multiple projects that enable an implicit form of hierarchy - Those are the ones this feature is useful for.
  2. Those that use multiple disjoint projects where no default can be set - those are the ones who don't want this feature.

Maybe a compromise could be found, where a default can be present but must not be. If no default project is present, the current approach should be taken.
What about that?

@delvh commented on GitHub (Mar 5, 2021): Well, I can understand your request, but there are two sides to that feature: 1. Those that use a single project for all issues or multiple projects that enable an implicit form of hierarchy - Those are the ones this feature is useful for. 2. Those that use multiple disjoint projects where no default can be set - those are the ones who don't want this feature. Maybe a compromise could be found, where a default **can** be present but **must not** be. If no default project is present, the current approach should be taken. What about that?
Author
Owner

@lunny commented on GitHub (Mar 5, 2021):

We can add options on repository settings.

@lunny commented on GitHub (Mar 5, 2021): We can add options on repository settings.
Author
Owner

@delvh commented on GitHub (Mar 5, 2021):

Yes, exactly. But a nil default value should be a valid case.

@delvh commented on GitHub (Mar 5, 2021): Yes, exactly. But a `nil` default value should be a valid case.
Author
Owner

@zaha commented on GitHub (Mar 5, 2021):

Yes, you are completely right. I wanted to suggest this as an option for people that only needed a single board. At least in my head, seems like I completely forgot to spell that out in the description, my bad. 😅

An option on the repository settings would be perfect! 👍

@zaha commented on GitHub (Mar 5, 2021): Yes, you are completely right. I wanted to suggest this as an option for people that only needed a single board. At least in my head, seems like I completely forgot to spell that out in the description, my bad. 😅 An option on the repository settings would be perfect! 👍
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#6962