An alternative would be to integrate with taiga (cf also #266) but that does mean hosting a taiga instance for people wanting to use this feature.

Maybe we could investigate both and just have a configuration boolean to use one or the other approach.

+1 on the Kanban board.

For this one, would you add additional states for issues on the kanban board? i.e. an issue on Board 1 is "in progress"

Couldn't we use a custom field: board: In Progress, Qeueud, WIP, Done.

Moving tickets would change that field up until the Done column that would close the ticket. Does that make sense?

I think a custom field would be nice indeed, the UI should dynamically build the board columns based on the field that way the project admin can choose how many columns and their name he wants for the project.

AFAIUI, the "boards" usually have these charateristics:

• a board can have 1..n columns, with the ability to name columns on a per-board basis
• an issue (or PR) can be added to multiple boards (although, not usually twice on the same board)

@jperrin might know more about the requirements here...

an issue (or PR) can be added to multiple boards (although, not usually twice on the same board)

Since we're using 1 board/project I'm not sure we could fullfill this one, unless we implement a way to share a ticket between multiple projects.

Perhaps you could do multiple boards by instead of having a 'board' custom field, have a custom field boolean 'board'.

Then you make custom field 'foo' and set board on it and it's a board, and you make custom field 'bar' and set board on it and its another board and you make custom field 'baz' and don't set board on it and it's just a custom field.

Then in issues you can choose what you want to display, etc.

The last update was 3 years ago, in 3 years before no decision about actionable tasks, I'm going to close this issue for now to reduce our backlog.