However the reason I moved back to Trello was the interface was a bit old-fashioned, and I found it hard to get my team on-board on kanbanflow wheras it was really easy to get them going on Trello.
It’s always surprising to me how many “lean” and “agile” productivity tools completely focus on the artifacts and seem to have skipped the core concepts entirely.
It's a bummer because in the current state, Wekan doesn't really provide much real management value. I really wanted to use it for Kanban, because it's one of the flagship applications of the fantastic Sandstorm cloud platform (https://sandstorm.io), to introduce some colleagues to both concepts at the same time... but I guess I will only show them about the later.
Well at least it implements subtasks (checklists)!
Yes, Wekan does not have those features yet. Anyway, Wekan is being actively developed and features added. Wekan is friendly community driven project and welcomes all contributions.
Some have commented on Wekan GitHub issues that they prefer to use Wekan, because some others project management tools are overkill, or don't have the same usability as Wekan. It depends on use case.
Likewise sub-boards and meta-issues. If we're doing agile properly then each card represents a user-facing deliverable. Allowing meta-issues encourages doing the wrong thing.
Limiting work in progress I've achieved by having people assign themselves to cards, and questioning those who are on multiple cards. In the cases where we're violating our work-in-progress limit, I'd rather have the board reflect reality than not.
Having used it for some projects as an alternative to JIRA, Trello, GitLab boards, and a few others that I tried, I think it's not perfect, quite hard to use for non-tech users, but much better than most of the alternatives.
The number of details/settings available is great compared to Trello or GitLab. The pricing/hosting is great compared to JIRA. The non-tech usability is much better in JIRA and Trello, but for a tech team, it has many small things/shortcuts like ones you already use in their IDEs which is really great.
There are hundreds of tools like this, and I tried maybe 20 or 30 of them; the thing is, there is no perfect tool out there, and there won't be as use cases for such a tool can be extremely different! YouTrack gets a lot of points right for a tech team from my experience though.
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.
Or a set of policies (solve in 4hours or less)
For the different tickets... It's the most powerful tool of the Kanban Method
Things that most actual Kanban flows have that no one has built into a decent product[0]:
The actual content of each work item is the least important part of Kanban; it could be a hyperlink for all I care. Kanban is about managing the flow, not managing the work.[0] Please prove me wrong if there is such a product out there!