Kanban board

[adelowo]

Fixes #3476

• Move Issues between Boards
• add Project to current Issue
• view project
• create a project
• create Issue during viewing project
• select project during create Issue
• add Board to an existing Project
• delete Board from a project
• rename Board title
• Individual boards
• Organization boards
• Repository boards

Definitely another PR:

• Location of cards in the project board. Right now, cards location in a board cannot be persisted - i.e move card X above card Y in the same board.

@rudineirk UI suggestion ( from #3476 (comment) ) was used.

[sapk]

Just quickly looking at it, it seems good overall. I have found some quirks that must come from the fact that some code in this PR as some history.

[sapk]

The lint tool make golangci-lint suggest some changes that need to be taken in account (unsed, duplicate, ...).

[lafriks]

As I understand projects are per-repository not per-organization, right?

[adelowo]

Yes

[lafriks]

How hard would it be to change that to be organization wide like github?

[adelowo]

Should not be too complicated. But GitHub has both repo and organization wide projects.

[gary-kim]

Having both organization and repository projects would be really nice. Thank you @adelowo

[andrewgdunn]

I'd vote for Individual, Organizational, and Repository level projects/workboards.

• For personal it would be nice to be able to allow viewing of the workboard (e.g. let others know what you're planning to work on)

If anyone wants to swoop in and assist on UX/UI work related to what @adelowo is doing I'd be happy to directly fund that effort.

[gsantner]

just my 2cents:
why keep merging back and forth and having one big PR instead of "base" kanban PR & implementation and do then another PR(s)?
guess smaller PR is also a lot easier&faster to review.
(I mean, thats by some way suggested already by the description, but still there are many points open for the suggested initial base version.)

[adelowo]

It will be squashed eventually. Secondly, these features are tightly coupled.

[lunny]

Please resolve the conflicts.

[adelowo]

Done @lunny

[techknowlogick]

@adelowo is this still WIP? Can I remove the label?

Edit: It looks like most of the checkmarks you have listed above are done, and I think the rest could be implemented in a later PR.

[adelowo]

@techknowlogick working on this during the weekend. Can strike off a few more by then and
the rest can come in another PR

[lunny]

@adelowo I suggest to move this to v1.12 since we need more time to review it. It's a big feature.

[adelowo]

@lunny Makes sense

[6543]

for confilct resolve:

• Comment Type 25 is now Used so 26 is the next free one
• public/js / public/css can be removed completly
• migration only nee higher number
• modules/setting/repository.go: simple confilct happend by end of list issue of git
• routers/repo/issue.go same thing as last one

[codecov-commenter]

Codecov Report

Merging #8346 into master will decrease coverage by 0.19%.
The diff coverage is 27.22%.

@@            Coverage Diff             @@
##           master    #8346      +/-   ##
==========================================
- Coverage   43.73%   43.54%   -0.20%     
==========================================
  Files         631      637       +6     
  Lines       69873    70821     +948     
==========================================
+ Hits        30561    30836     +275     
- Misses      34352    34982     +630     
- Partials     4960     5003      +43     

Impacted Files	Coverage Δ
models/error.go	34.81% <0.00%> (-0.61%)	⬇️
models/migrations/migrations.go	4.66% <ø> (ø)
models/migrations/v146.go	0.00% <0.00%> (ø)
modules/auth/repo_form.go	42.34% <ø> (ø)
modules/structs/repo.go	54.54% <ø> (ø)
routers/api/v1/repo/repo.go	62.15% <0.00%> (-1.41%)	⬇️
routers/repo/milestone.go	0.00% <0.00%> (ø)
routers/repo/setting.go	14.85% <0.00%> (-0.18%)	⬇️
routers/user/home.go	60.88% <ø> (ø)
routers/user/profile.go	48.46% <0.00%> (-2.34%)	⬇️
... and 30 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f50364a...a48f839. Read the comment docs.

[mooror]

Huge thank you to everyone who has worked on this feature. This is going to be a game changer for the company I work for. Looking forward to it.

Long live Gitea!
Benjamin

[vtolstov]

i'm use gitea from the beginning, and like this feature. why it not merged yet? i think that if it will be merged as soon as possible we can have many testers and contributors, for now this pr looks like really huge and not so many people can provide some useful help

[jaqra]

@vtolstov waiting for @lafriks 's review, then this will be merged if no any problem

[techknowlogick]

🚀

[a1012112796]

Suggest add some screenshots to the REAME.md file.

[patcito]

As promised, here is my PR that builds on @adelowo work #12506 Let me know what you think.

[philiplb]

Nice! Awesome work! <3

[TheTechRobo]

in migration there is no selection for project board migration

[6543]

@TheTechRobo because project migration is not supported jet

[Extarys]

• You should add this feature in the comparison table 😄
• Any ETA when this will be part of a release? Not to rush or anything, I'm not familiar with the release cycle and methods of Gitea. (I'll use Nextcloud Deck on my personal instance in the mean time as I'm just planning the project right now)

Fun sidenote: I'm working on a new project for fun at home and I was checking out nextcloud Deck and Notes, but for my use (only this project) I find it too bloated and since I'll be writing some code, Gitea came to mind.

I'm currently checking out Taiga in a docker container, but of course I would prefer everything to be at the same place (ie: with the code and the issues on Gitea) I kind of like their point system to prioritize (which is not a priority here)

Quite funny this issue was merged recently! 🙏

Another sidenote: I've been seeing lots of open source projects belonging to small companies that got bought by big tech giants and closing their OSS or not contributing to the Open-source dataset, etc and it was refreshing browsing Gitea repo today. Good job to everyone for releasing so many versions and committing so many new features! ❤️

@patrickdevivo Awesome PR! Would it be a good idea to have an option to tag the issue automatically once it was added to the kanban? [ie: kanban/low priority] I believe it would help when browsing the issue tracker to know which one is already planned/tagged or just read.

[6543]

@Extarys @TheTechRobo please open a NEW issue to discuss such things on

all you post on this Merged pull will fall out of our minds and in the end will be ignored
there is no good in commenting at a closed pull -> you should just reference them :)