If you want to do Kanban right, double down on making it possible to design actual Kanban workflows. Pretty ticket UI with checklists and GIFs must be secondary to this goal. Things that most actual Kanban flows have that no one has built into a decent product[0]: - Nested columns in lanes - Rows for class-of-service - WIP limits (per lane, per column, and per class-of-service) - Sub-boards for meta issues The actual…
The product I've been working on the last few months has all the things you listed, mostly: http://cwkanban.com/ . It's been a huge help to my own team's workflow. But it's not general-purpose like Wekan or Trello; it's focused on workflow for managed IT and at the moment only pulls ticket data from ConnectWise, software for managed services providers.
Not trying to be a dick, but that sounds... kind of weasely.