Kanban board

[HLFH]

Hi,

It would be great to add a Kanban board feature to Gogs. GitHub and GitLab are doing it.

Thanks,
HLFH

[skrzepto]

Do we force the generic 4 columns (backlog, ready, wip, review) or do we allow the admin to add any column they wish?

[HLFH]

Yes at least, we should be able to have 4 columns (backlog, next, in progress, released). Wekan allows also to add any column we wish. IMHO, 4 columns by default would be interesting. But we should be able to change the number and the names of the columns.

[skrzepto]

But we should be able to change the number and the names of the columns.

Could you elaborate what you mean by number? Do you mean the position of the column or the amount of columns?

[HLFH]

The amount of columns. And in fact, on Wekan, the position can also be changed just by moving the mouse. But I don't expect something big for the first possible implementation of this feature within Gogs.

[dasyrw9hfh]

Having a kanban sounds like unnecessary bloat to me...

[skrzepto]

@dasyrw9hfh

Having a kanban sounds like unnecessary bloat to me..
Depends who you are talking with. In my opinion it would be nice feature to implement.

My thoughts to satisfy both sides would be to leave it off default for new repos and the repo admin would have to tick a box to enable the kanboard feature. Thoughts?

Also design it so its decoupled from the rest of the services so it doesn't create a hindrance.

[genofire]

the column could easy be a tag on the issue.
On this way the name and order of the columns must only be stored on the project.
And a view for these columns with easy adding a tag on the issue and moving this issue.

[skrzepto]

@genofire thats assuming if we focus on one board only? Should there be the ability to have multiple boards per repo or just one?

[genofire]

for me, one per repo is enought -> but github could use multiple, so for other users this could be more interesting

So the kanban tag on issue could be something like boardId_columnname or boardname_columnname. (another option would be two tags).

My favour would be that the columnname is in the tag name.

• Never mind the a renameing of the column would destroy the relationship. (the issues has not anything todo with the new column)
• Or we have to handle a renaming of the column by renaming all tags on all issues in a repo.

[thibaultmeyer]

If Kanban tab could be disabled (like PR or Wiki) it could be nice. Kanban board is not necessary needed on all repos.

[skrzepto]

@genofire I agree one repo would be enough. And I think a unique ID to refer to the column would make sense for O(1) rename since the board_column_name can change while the uuid stays the same.

If Kanban tab could be disabled (like PR or Wiki) it could be nice. Kanban board is not necessary needed on all repos.

@0xBAADF00D 100% agree, I started working on a initial implementation and that was the first thing I did.

[genofire]

If you need help ....

[skrzepto]

@genofire I think for the most part the backend code is close to finish so next step is UI/UX which is not my strong suit.

Regarding the backend

Just have a question about how the issues should be returned in the front end. Example

---

Option 1:
Should we return an array of all the issues in JSON format and have JS iterate the list of issues and place them on the board

Option 2:
Or have the backend do the ordering and return {'column1': issue_1, 'column2': 'issue_2, etc...}

---

I'm leaning on Option 1 because it offloads the workload to the user but thats just a personal opinion. Thoughts?

[genofire]

I like to handel it on client side, for drag and drop it would be the best way i thing. (Option 1)

{
"column1": {"id":1,"position":2,"issues": []},
"column2":
    {
     "id":2,
     "position":1,
     "issues": [
         {"id":4,"title":"never ending",...}
      ]
   },
}

[mhtsbt]

If anyone is interessted in working on this, feel free to contact me. I started working (https://github.com/mhtsbt/GogsBoard) on a gogs-powered kanban board. It's a seperate application that connects through the api:

[lunny]

@mhtsbt could you also send a PR to Gitea? I think many maintainers of Gitea could review your code.

[RcrdBrt]

Ping?

[sebastianmacias]

+1 Kanban implementation

[jerrdasur]

As I see @mhtsbt ends his work with gogs canban project. Does anyone work on this in current time?

I would be glad to offer my help with this.

[kstan79]

Hi, is this plugin merged into master?

[RcrdBrt]

Nope, although it would be a very nice addition.

…

On Dec 21, 2017 5:47 PM, "Ks Tan" ***@***.***> wrote: Hi, is this plugin merged into master? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#3716 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABSqmhQrhW1lH_W3OHHkqK_R3qhH4nK6ks5tCouNgaJpZM4KLOpH> .

[Seanxwy]

i want

[alexandr85]

and I want too 👍

[elmbrent]

This would be great!

[dzcpy]

Please, this is very useful

[kbaegis]

+1

[zlbabe]

Ping !

[Xsmael]

any update on this ?

[ckotthaus]

+1

[LucasManerich]

+1

[gemurdock]

I think a lot of people would love something like this. I know I use the Kanban board for every project that is not simple.

[celedev97]

+1

[k9t9]

Is there any update on this feature ( 5 years on the pipe now ) ?

[Tha14]

Any update on this? It could really help with development.

[digitalextremist]

This is pretty much the only thing holding me back from migrating from GitLab

[genofire]

PS: gitea and forgejo has it already, i do not know how long, but here is a PR with screenshots of bugfixes there in 1.14.0 - 2021-04-11:
go-gitea/gitea#13437