Backstory

I build software and often wear tech-lead and project-manager hats. My rhythm has settled long ago: Agile Scrum, two-week sprints, Jira as the everyday home for work items. Practically the default for most teams. As long as the work stays flat, this stack carries you just fine.

When a sprint no longer fits in a list

Not every sprint is a queue of small defects. Sometimes a bigger piece lands in it: an issue that has to be decomposed into several subtasks, some of which split further. Almost immediately, links appear: one piece blocks another, something “contains” a neighbor, a third sits beside them and depends on both.

That is the point where the tracker UI starts fighting your pace. To adjust a link or a wording, I open another tab, then one more, then one more. And this repeats every sprint.

The cost of context

Planning is not the only place this hurts. To grasp the meaning of a task, an engineer has to open its parent. And that parent may itself be a subtask of something else. A chain of two or three parents is a normal day. Context spreads across tickets, and everyone reassembles it on their own.

The idea

At some point I caught myself wanting something very simple: to see all the connected work at once. Not the text inside one more ticket, but the picture on a single surface, where you can read what depends on what and what blocks what. And one more thing: I wanted to decompose in one motion, as if dropping a block onto a diagram. An idea, a node, a link, and the structure has already changed.

A second wish appeared right after that: do this together with the team. Sit down, sketch the structure quickly, agree, and then carry the result into Jira cleanly. Not the other way around.

Plugins and detours

The first stop was Jira plugins and add-ons. There turned out to be many, and most of them leaned toward roadmaps, yet another Kanban board, or a polished chart for reporting. Useful in their lane, but not what I needed: a real task dependency graph you can grab and shape, not only admire from above.

I never found a fit, so I decided to build my own. Since then the original idea has grown into features, collaboration modes, and a hundred small comforts that make shared planning bearable.

Where things stand

Today it is an MVP. Jira and Yandex Tracker integrations are technically in place: the interactive board can lean on live data. What comes next will depend on usage; it might eventually grow into something bigger - a task tracker of its own with its own model of planning. Even without that, the starting point stays simple: fewer tabs, more clarity, one board where links read like a graph.

If this resonates, follow the Telegram channel for build updates and beta news.