Description
Feature Description
Hi,
I’m opening a feature request to talk about project kanban improvements that will make it more suitable in an Agile team with decent size (10 to 12 person). I spent some times reading the code to package a list of features with a good effort/improvements ratio.
I also read passed issues more or less linked to this one: #26456 #13814
I have passed experience with Trello and found the UI really efficient, some of my proposals are inspired by it.
You’ll find below the features I’d like to bundle in a PR
Increase the number of issues visible (limit scrolling)
- Decrease card font size
- Use all width of the screen (wide mode)
- Remove headers: I think headers (board edition buttons and organization tab selection) take too much vertical space. We could use a toggle full screen button to hide them on demand or re-arrange the view to completly remove them. Option 2 would break common design of gitea, not sure it’s a good idea. What do you guys think?
Add issue filters to kanban view
The goal is to be able to use the board as a real project management tool: filter by assignee or owner, sort by due date etc.. After reviewing the filters in the issue list page I found that all the features are already implemented there.
Consequently, I think adding it to the project kanban view can be a good idea in terms of effort/improvements ratio. After reading the code I think it’ll require the following modifications:
- Add templates/repo/issue/filters.tmpl to templates/project/view.tmpl
- routers/web/org/projects.go::ViewProject should use part of routers/web/repo/issue.go::issues to filter issues and populate filters
It looks to me that the routers/web/repo/issue.go::issues function should be in a service or model layer instead of handler as it can be used by different module. Do you agree? What would be the best place to move this function?
Before I start to work on a PR, I’d like to have some feedback from the maintainers:
- Do you plan to add those kinds of features in near future?
- Would you agree upon merging a PR with the listed features above?
- Is there an optimal time window to work on it (avoid merge conflict)?
Also any feedback from the whole community is welcome: other features, thumbs up if interested by the proposal, push in the right direction?
Screenshots
No response