See delivery move without turning your spec into a status spreadsheet.
Tracker reads the current revision's epics, flows, and flow steps, then gives the team one operational view of what is TO DO, DOING, and DONE.
Product walkthrough
Tracker, in context.
Demo project data shown for illustration.
Screen 01 / 02
Delivery pulse
Delivery pulse across seven logistics flows
The working path
A focused loop around the same project context.
A delivery lead wants to see whether the checkout work is actually moving through Build and QA, including the partially completed steps hidden inside a flow.
- 01
Choose All or a delivery phase to focus the workspace on the relevant flows.
- 02
Update a flow or individual step as work begins and finishes; step-specific phases can override the flow default.
- 03
Read the recalculated Delivery pulse for the visible scope, grouped by epic and including unassigned work.
Using Tracker
Tracking state persists independently of publishing a revision. People with read access can inspect it; editing requires project write access.
Continue exploring