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.
Customer Feedback
Feature Requests
Bug Reports
Features
Tasks
FeatureFEAT-1
Billing
Stable
FeatureFEAT-2
Invoices
Stable
TaskTASK-26
Show the amount due on each invoice
Done
AI Email6
Can I pay it in parts?
+5 more - click to expand
Completed
RequestPFR-5
Split large invoices
Promoted
FeatureFEAT-3
Pay in instalments
Stable
Task3
Email the reminder as well
+2 more - click to expand
Done
Bug ReportBUG-14
Second instalment shows the wrong due date
Resolved
Customer Feedback
- Can I pay it in parts?+5Completed
Feature Requests
- PFR-5Split large invoicesPromoted
Bug Reports
- BUG-14Second instalment shows the wrong due dateResolved
Features
- FEAT-3Pay in instalmentsStable
Tasks
- TASK-33Email the reminder as well+2Done
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.
Pay in instalments
Lineage ยท Pay in instalments
Customer Feedback
- Can I pay it in parts?+5Completed
Feature Requests
- PFR-5Split large invoicesPromoted
Bug Reports
- BUG-14Second instalment shows the wrong due dateResolved
Features
- FEAT-3Pay in instalmentsStable
Tasks
- TASK-31Split an invoice into three paymentsDone
- TASK-32Remind before each instalmentDone
- TASK-33Email the reminder as wellDone
Sessions
- SSID-3Payment in instalmentsCompleted
- SSID-6Email the reminder as wellCompleted
- SSID-5Wrong due date on instalmentsCompleted
Releases
- REL-2Instalment paymentsReleased
- REL-3Email reminders and amounts dueIn progress
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
Customer Feedback
Feature Requests
Bug Reports
Features
Tasks
FeatureFEAT-5
Reminders
Stable
TaskTASK-28
Let customers pick the reminder day
To do
Meeting notes7
Reminders check-in
+6 more - click to expand
Completed
RequestPFR-12
Payment reminders by text message
In review
Open
View lineage
Promote to feature
Promote to task
AI Voice5
Bookkeeping at month end
+4 more - click to expand
Completed
RequestPFR-9
Sync invoices to accounting software
In review
Feedback widget2
Sending forty invoices at once
+1 more - click to expand
Completed
RequestPFR-15
Send invoices in bulk
New
Customer Feedback
- Reminders check-in+6Completed
Feature Requests
- PFR-12Payment reminders by text messageIn review
Open
View lineage
Promote to feature
Promote to task
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?
Instalment payments
Lineage ยท Instalment payments
Customer Feedback
- Can I pay it in parts?+7Completed
Feature Requests
- PFR-5Split large invoicesPromoted
- PFR-10Remind me before an instalment is duePromoted
Features
- FEAT-3Pay in instalmentsStable
Tasks
- TASK-31Split an invoice into three paymentsDone
- TASK-32Remind before each instalmentDone
Sessions
- SSID-3Payment in instalmentsCompleted
Releases
- REL-2Instalment paymentsReleased
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