Global kanban with filters #11442

New Issue

GiteaMirror · 2025-11-02T09:37:49-06:00

GiteaMirror commented

2025-11-02 09:37:49 -06:00

Originally created by @KlavsKlavsen on GitHub (Aug 11, 2023).

Feature Description

I think it would be great if gitea had a "org level kanban" - that could list issues from ANY project within the org - with issue filtering on so one could f.ex. "list issues from 1 particular project".. OR from a "parent project" - which has subprojects (f.ex. view all 'internal tasks - no matter which subproject they were in) - or filter on "assignee" - so one can see all ones tasks and their "status in kanban flow" across any project..

This is actually our main hiindrance from using only gitea for tasks and planning

Screenshots

No response

Originally created by @KlavsKlavsen on GitHub (Aug 11, 2023). ### Feature Description I think it would be great if gitea had a "org level kanban" - that could list issues from ANY project within the org - with issue filtering on so one could f.ex. "list issues from 1 particular project".. OR from a "parent project" - which has subprojects (f.ex. view all 'internal tasks - no matter which subproject they were in) - or filter on "assignee" - so one can see all ones tasks and their "status in kanban flow" across any project.. This is actually our main hiindrance from using only gitea for tasks and planning ### Screenshots _No response_

GiteaMirror added the topic/projects type/proposal labels 2025-11-02 09:37:49 -06:00

GiteaMirror commented

2025-11-02 09:37:50 -06:00

@denyskon commented on GitHub (Aug 11, 2023):

Org-level kanban boards are already possible with Gitea, but not the filter options and similar. Could you please rephrase your feature proposal accordingly?

@denyskon commented on GitHub (Aug 11, 2023): Org-level kanban boards are already possible with Gitea, but not the filter options and similar. Could you please rephrase your feature proposal accordingly?

GiteaMirror commented

2025-11-02 09:37:50 -06:00

@KlavsKlavsen commented on GitHub (Aug 14, 2023):

How can I do an Org level kanban board? Only thing I've been able to do, is to make a project directly under org - and then a kanban board for that. Then I can have ONLY ONE project and assign all issues to that project - for it to show up on that kanban board.
Thats NOT the same at all.
Point is that you should be able to have projects.. and issues assigned to those projects show up on the project kanban board..
BUT - then a global view kanban board with filtering - should be possible (as an alternative to having kanban board per project).

This way, you can have your per project kanban board (and some users may only have access to that) - but managers f.ex. - can use the org-level board with filtering - and view f.ex. one users tasks status - across all projects.

The filtering is the same as "the existing swimlanes" feature request - which is useful both for "per project" kanban boards and for a org level/global project-wide kanban board.

@KlavsKlavsen commented on GitHub (Aug 14, 2023): How can I do an Org level kanban board? Only thing I've been able to do, is to make a project directly under org - and then a kanban board for that. Then I can have ONLY ONE project and assign all issues to that project - for it to show up on that kanban board. Thats NOT the same at all. Point is that you should be able to have projects.. and issues assigned to those projects show up on the project kanban board.. BUT - then a global view kanban board with filtering - should be possible (as an alternative to having kanban board per project). This way, you can have your per project kanban board (and some users may only have access to that) - but managers f.ex. - can use the org-level board with filtering - and view f.ex. one users tasks status - across all projects. The filtering is the same as "the existing swimlanes" feature request - which is useful both for "per project" kanban boards and for a org level/global project-wide kanban board.

GiteaMirror commented

2025-11-02 09:37:50 -06:00

@KlavsKlavsen commented on GitHub (Aug 16, 2023):

such a kanban view - would have to pull "all possible columns" - from all projects - to show their state in a global kanban view.. and that might just make it fairly useless.. especially as gitea does not seem to map "columns" - to a seperate "issue flow" structure.. which it really should to clean this up.

@KlavsKlavsen commented on GitHub (Aug 16, 2023): such a kanban view - would have to pull "all possible columns" - from all projects - to show their state in a global kanban view.. and that might just make it fairly useless.. especially as gitea does not seem to map "columns" - to a seperate "issue flow" structure.. which it really should to clean this up.

GiteaMirror commented

2025-11-02 09:37:50 -06:00

@KlavsKlavsen commented on GitHub (Aug 16, 2023):

a usecase we would like to support is this:
We have about 15 projects.. we have a kanban/project for each of them - so the project owner(s) can plan and show their progress for each project..
Along side that we have standups - and our teammembers work on multiple projects.. so we'd like at standup to show a single kanban - that shows issues assigned to user X (the swimlanes/filter need for kanban - ticket exists with PR) - across all projects.

alternatively one COULD add "user" filter to the org level users view (its missing that) - to atleast be able to see all issues - but then its not aligned with the status display (kanban columns) that kanban does so well.

@KlavsKlavsen commented on GitHub (Aug 16, 2023): a usecase we would like to support is this: We have about 15 projects.. we have a kanban/project for each of them - so the project owner(s) can plan and show their progress for each project.. Along side that we have standups - and our teammembers work on multiple projects.. so we'd like at standup to show a single kanban - that shows issues assigned to user X (the swimlanes/filter need for kanban - ticket exists with PR) - across all projects. alternatively one COULD add "user" filter to the org level users view (its missing that) - to atleast be able to see all issues - but then its not aligned with the status display (kanban columns) that kanban does so well.

GiteaMirror commented

2025-11-02 09:37:50 -06:00

@denyskon commented on GitHub (Aug 19, 2023):

So you mean that you have sort of an issue dashboard for the whole organisation, which by default displays issues from every project, and then can be filtered to display e. g. issues by assignee?

@denyskon commented on GitHub (Aug 19, 2023): So you mean that you have sort of an issue dashboard for the whole organisation, which by default displays issues from every project, and then can be filtered to display e. g. issues by assignee?

GiteaMirror commented

2025-11-02 09:37:51 -06:00

@KlavsKlavsen commented on GitHub (Aug 24, 2023):

@denyskon yes - and I just had one of my employees make a PR to enable just that filtering in global issues https://github.com/go-gitea/gitea/pull/26661 - but that does not show "how far along" each of the issues shown are.. This is something the Kanban board does well.. (with swimlanes as its called for kanban board -which gitea does not have yet, to show only 'issues assigned to user X').
So if a global kanban board were possible (an option in global project perhaps - to 'show all issues - no matter which project they belong to') - and then id would have to "show columns from all projects' too - and hopefully there would be a lot of "duplicates - that could be merged into same column' - which IMHO would be helped if you could assign a "label" to a column (see https://github.com/go-gitea/gitea/issues/26704 )- so if you used org-level labels for your issues (as we do) - then it would be easy to get a nice "global view" kanban board.. Which, if it got filtering (aka. swimlanes - see other issues on this) - then you could see all tasks for assignee X - and their status - across any project they worked on.

We want issues to stay with the repo they are about.. and we enjoy that we can have a kanban board for each - but we also need a global view.

For now we're going to try to assign ALL issues to SAME project (but different milestones - as milestones belong to either org or repo) .
This would mean that we would have 1 kanban board - showing ALL issues.. and we can then add the "swimlane PR" that is already there to filter by "assignee" - and add filtering by label - to show f.ex. only tasks of specific label
That does mean we can have only 1 project (global).. but that should be enough for us for now.. But if you need multiple projects, IMHO a kanban that could show "all issues" - would be helpful.

@KlavsKlavsen commented on GitHub (Aug 24, 2023): @denyskon yes - and I just had one of my employees make a PR to enable just that filtering in global issues https://github.com/go-gitea/gitea/pull/26661 - but that does not show "how far along" each of the issues shown are.. This is something the Kanban board does well.. (with swimlanes as its called for kanban board -which gitea does not have yet, to show only 'issues assigned to user X'). So if a global kanban board were possible (an option in global project perhaps - to 'show all issues - no matter which project they belong to') - and then id would have to "show columns from all projects' too - and hopefully there would be a lot of "duplicates - that could be merged into same column' - which IMHO would be helped if you could assign a "label" to a column (see https://github.com/go-gitea/gitea/issues/26704 )- so if you used org-level labels for your issues (as we do) - then it would be easy to get a nice "global view" kanban board.. Which, if it got filtering (aka. swimlanes - see other issues on this) - then you could see all tasks for assignee X - and their status - across any project they worked on. We want issues to stay with the repo they are about.. and we enjoy that we can have a kanban board for each - but we also need a global view. For now we're going to try to assign ALL issues to SAME project (but different milestones - as milestones belong to either org or repo) . This would mean that we would have 1 kanban board - showing ALL issues.. and we can then add the "swimlane PR" that is already there to filter by "assignee" - and add filtering by label - to show f.ex. only tasks of specific label That does mean we can have only 1 project (global).. but that should be enough for us for now.. But if you need multiple projects, IMHO a kanban that could show "all issues" - would be helpful.

GiteaMirror commented

2025-11-02 09:37:51 -06:00

@vvrein commented on GitHub (Sep 11, 2023):

This sounds like that what is implemented in GitLab. In parent group you can see all the issues from nested repositories and subgroups with their repositories in a form of the list or the kanboard.
And you can filter the issues by assignee, label, author, milestone, and so forth.

But gitlab is very heavy and complicated to setup 😅.
It will be great pleasure once to see this feature in Gitea ❤️

@vvrein commented on GitHub (Sep 11, 2023): This sounds like that what is implemented in GitLab. In parent group you can see all the issues from nested repositories and subgroups with their repositories in a form of the list or the kanboard. And you can filter the issues by assignee, label, author, milestone, and so forth. But gitlab is very heavy and complicated to setup 😅. It will be great pleasure once to see this feature in Gitea ❤️

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#11442