Skip to main content

Lineage

Know why it was built, and what became of every request.

Lineage connects your product work the way it happened: the customer conversations behind each request, the feature it became, the tasks and coding sessions that built it, and the release that shipped it. Start from any of them and follow the line either way.

Read the user guide

From a feature

Why are we building this?

Open a feature's lineage and the answer is people, not a line in a spec: the customer conversations its requests were picked out of, and everything built and shipped for it since.

Meet Software Inc, a fictional company that sells invoicing software. Every name in these pictures is sample data.

  • Read what they said.

    On the map, choose any card to read it in the panel beside it: the conversation, the request, the feature, a task.

  • Your team's input beside theirs.

    Interests recorded by hand sit with the conversations: a customer's interest, a teammate's input, a market signal.

  • Everything since.

    The bug reports linked to the feature, the coding sessions that worked on it, and the releases those sessions shipped in.

  • Keep following.

    View lineage on any card moves the map to it. Features, requests, bug reports, tasks, sessions, releases and customer conversations each open their own.

From the customer's side

What happened
to that request?

Start from a customer conversation or a request. If it became something, its lineage runs on to the feature, the session that built it and the release it shipped in. If it didn't, it is an unlinked request: counted in the toolbar, on a row of its own with the conversations it came from.

  • Decide on it from the map.

    Right-click a request that is New or In Review to promote it to a feature or a task. The map draws the new link as soon as it exists.

  • Turn a feature into work.

    On a feature, Create task, or Generate tasks when it has none yet.

  • Change it where you see it.

    A feature, a request, a bug report or a task can be changed in the panel beside the map, just as on its own page.

  • Live as your team works.

    When anyone changes a status or makes a link elsewhere in the app, the map updates without a refresh.

Read moreFeature requests

Sample data

From a release

What did we ship,
and for whom?

A release's lineage shows the work it shipped and the coding sessions that did it, then the features, the requests and the customers who asked. From a session, the same line answers an engineer's question: why is this code the way it is?

Sample data

  • Everything it shipped.

    Every task, bug report and session under In this release, found in the commits or added by hand, with the session between each piece of work and the release.

  • Back to who asked.

    Through each task to its feature, to the requests promoted into either, and to the conversations each was picked out of.

  • From a coding session.

    A session's Lineage, in its rail, shows the tasks it worked on and, behind them, the feature, the requests and the conversations.

  • From a bug report.

    A bug report's lineage shows the conversations it came from, the sessions that worked on it and the releases they shipped in.

On plans that include lineage.

Read moreRelease manager

Just build it.

An idea or a backlog. Either way, you're not building alone.

Get started