Use tapd measure commands to query TAPD measurement data.
All measure commands use the configured TAPD credentials from tapd login or
the TAPD_ACCESS_TOKEN / TAPD_CLIENT_ID / TAPD_CLIENT_SECRET environment
variables.
Measure commands require a workspace:
tapd measure life-times --workspace-id 123456 --entity-type story --entity-id 1111112222001000001The short form is also supported:
tapd measure life-times -w 123456 --entity-type story --entity-id 1111112222001000001Measure commands default to table output:
tapd measure life-times -w 123456 --entity-type story --entity-id 1111112222001000001Use JSON when piping to another program or when you need the full SDK response shape:
tapd measure life-times -w 123456 --entity-type story --entity-id 1111112222001000001 --format jsonQuery status transition life times for a story, task, or bug:
tapd measure life-times \
-w 123456 \
--entity-type story \
--entity-id 1111112222001000001Supported entity types are story, task, and bug.
Useful optional flags:
tapd measure life-times \
-w 123456 \
--entity-type bug \
--entity-id 1111112222001000001 \
--created "2026-01-01~2026-01-31" \
--limit 50 \
--page 1Request specific fields from TAPD:
tapd measure life-times -w 123456 --entity-type task --entity-id 1111112222001000001 --fields id,status,time_cost,createdThe measure command implementation currently lives in:
internal/cmd/measure.go
When adding or renaming measure commands:
- Reuse the typed SDK methods from
github.com/go-tapd/tapd. - Keep table output compact and use
--format jsonfor full response data. - Update
features.md. - Update this document.
- Regenerate shell completion files if they have been installed locally.