This is a minified code.

Your comment was the first, but it's the hardest to answer.

I started doing this project when a new manager joined the team. And his first decision was to change the processes by rebuilding the kanban board. The team as a whole was initially satisfied with the board, which had been built for a long time with the previous two managers. Everyone began to propose their requirements for the kanban board, but the new manager did not hesitate to do as he saw fit. And in the future, this story was repeated with new managers.

If you take into account all the wishes, then the board becomes very large, both in width and in height. That's why I don't criticize new managers. In many ways, this is a consequence of the tracker's functionality.

Different types of work have different stages. For example, a developer needs a "code review" column, someone needs an additional "approval" column, etc. My idea was to give each type of work its own board. And on the task card, display which subtasks are currently being worked on. As a result, we would have unloaded the main kanban board, and the kanban boards for work tasks would have become more flexible.

It also provides new opportunities for analytics. Or here is the flexibility in creating tasks, for example, add an "analytics" task at the testing stage. For me, ooko is an experiment with a hierarchy of tasks, so what the pros or cons are remains to be seen. Something like that

Let me philosophize a bit: Stability gives you the opportunity to take the next step, diversity gives you the opportunity to choose a new direction.

I love the statement not so specific to this conversation but in general. Completely agree.

Yes

The limit can be specified per board (process). This is my vision of an electronic kanban board. Perhaps in the future I will add an indication to the columns, but now I want to check my guesses.

Using vibe coding, you will not be able to do such a service in such a short time. In addition to the goal of researching my kanban vision, I also experimented with an architecture that allowed me to achieve the required productivity and ease of development. AI is not that cool yet

Yes, registration is required. This is both a demo and a working service that is used by a dozen teams.

So it's not a demo then.

It would help a lot of you added an actual demo. Or simply changed the wording to say "make a free account here to test it".

Perhaps you're right and it's worth changing the wording. But those users who are not ready to register will not follow the link and I will not find out about them. And those who are ready will not pay attention to the wording of the link.

It takes most of the time to decide what to do next. I don't have so much energy and desire to do anything to try to do everything. The main way of promotion is advertising in search results. For me, it is the most effective and affordable in terms of quality for new users.

Trello does not work in Russia. You cannot install it on your server in the company's closed loop. There is no task number, there are no subtasks, you cannot see the progress of subtasks on the parent's board. There is no analytics. There is no page where you can view all the tasks that can be taken on. The service does not claim the laurels of solving all problems, but it is unique in its own way.

ooko.pro It's not just a demo, it's a working service and a lot of people use it every day. The presence of registration is both a necessity and a kind of barrier from disinterested users.

It's also a barrier to interested users. I'm one. I am currently using 3 kanban solutions for different needs. I'm always looking for better solutions, but I'm not going to invest much in something with no docs and one screenshot.

That said, your answer here tells me what I need to know about the product.