What Depensee can do now

Over the last few months, Depensee has moved from a concept to a working MVP. The original idea remains the same: not to replace a team’s existing tracker on day one, but to give it a separate surface where tasks, hierarchy and dependencies are visible together.

What already works

On the first visit, you can create a blank board, choose a demo board or bring in tasks from Jira and Yandex Tracker. Cards can be moved on the map, and their positions are stored separately from the tracker data.

Imports are currently read-only. That is deliberate: first, a team should be able to inspect the structure of an existing project without risking accidental changes in the source tracker.

The map understands three relation types: blocks, contains and relates. Blocking links show the direction of dependencies, parent-child links keep related work close together, and associative links add context. When there are many tasks and relations, a dedicated algorithm turns the graph into a readable structure: it reduces crossings and keeps the flow direction clear.

Integrations and the technical side

The integration layer lives in a separate library, trackerkit. That lets the Depensee backend work with one model of tasks and relations while Jira and Yandex Tracker specifics stay inside their adapters.

I also published a separate Habr article on how we approached task-graph drawing: from removing cycles to routing lines around cards. It is based on the Sugiyama method, a classic approach to drawing directed graphs.

What is next

The next step is improving the demo: making the first scenario clearer, removing rough edges and preparing the map for an open presentation.

If you want to follow the build, join the Telegram channel.