Some thoughts on a Kanban view for issues.

We need to specify:

  items to display
  columns for the board
  card format/fields
  swimlane (optional)

One mapping from an index display is:

  items to display - search results
  columns for the board - @sort field
  card format/fields - @columns display
  swimlane (optional) - @group

An example kanban board for @sort=status, @columns=id,title,assignedto,
@group=sprint (assuming the issues have a sprint property) like:

   Status   Backlog       Ready         Open       Testing      Closed
Sprint    +----------+ +----------+ +----------+ +----------+ +----------+
          | -------- | |          | |          | | -------- | |          |
24-10-02  | 1060     | |          | |          | | 1319     | |          |
          | new item | |          | |          | | title 4  | |          |
          | Fred     | |          | |          | | Renee    | |          |
          | ======== | |          | |          | | -------- | |          |
          | 2210     | |          | |          | |          | |          |
          | need fre | |          | |          | |          | |          |
          | Steve    | |          | |          | |          | |          |
          | -------- | |          | |          | |          | |          |
          |          | |          | |          | |          | |          |
          |          | |          | |          | |          | |          |
          +----------+ +----------+ +----------+ +----------+ +----------+
          +----------+ +----------+ +----------+ +----------+ +----------+
          | -------- | |          | |          | |          | |          |
24-10-16  | 1310     | |          | |          | |          | |          |
          | title 4  | |          | |          | |          | |          |
          | Renee    | |          | |          | |          | |          |
          | -------- | |          | |          | |          | |          |
          |          | |          | |          | |          | |          |
          |          | |          | |          | |          | |          |
          +----------+ +----------+ +----------+ +----------+ +----------+

Each card can be dragged to a new column and on drop, the back end is updated via
REST request to set the issue to its new status.

Consider a drag/drop javascript library:

  * https://github.com/SortableJS/Sortable
  * https://github.com/atlassian/pragmatic-drag-and-drop
  * https://github.com/ThibaultJanBeyer/DragSelect

Maybe use grid for layout of the columns/swimlanes.

Open issues:

  How to display on mobile or when width is too narrow.
  How to configure card layout. Consider a sub-template for each card style.
    That way an admin only needs to design the card level template similar
    to any other template.

Other references:

 Swimlanes: https://teamhood.com/kanban-resources/kanban-swimlanes/

 js kanban library: https://github.com/riktar/jkanban

My team uses Roundup to track the qualified presales 
leads we are working with. If you (or someone else) 
ever pursue this, we would definitely use it.

If you believe our input could be of any help, I'll 
happily chip in with our two cents on this.

Hi William:

Thanks for your interest.

Do you use Kanban outside of Roundup for your presales leads?

What form do your kanban chart takes, or what form would you like them to take:

  * how are columns labeled: e.g. by the stage in the sales funnel?
  * what is displayed on the Kanban cards: e.g. sales rep, dollar amount,
    client name, client contact?
  * are swimlanes used: e.g. per sales rep?
  * are work in progress limits per column useful?

I can't promise anybody will work on it, but gathering requirements is useful.

Also if you are willing, I would like to contact you off ticket to get some more
info about your roundup setup and use case.

-- rouilj