Flow
Menu

Reference

Time in state — how long a project's open work sits in each state

The get-project-metrics tool, and the REST call it is generated from.

RESTGET /api/v1/projects/{id}/metrics
MCPget-project-metrics

One row per status, readiness state and on, read back from the history of the project's work tasks: their status moves, every wait they were given and every blocks edge into them. open is how many are in that state at until, and open_days how long they have been; entered and left are how many times a task entered and left it during the window, and left_days how long each stayed. moves counts each pass from one state to another in the window, to a bare status when the task closed. completed is creation to completion for the tasks completed in the window. Days are nearest-rank percentiles, to one decimal; null where nothing was counted.

Parameters

  • idpath · required · string

    The project's proj_… id, as list-projects answers it.

  • sincequery · optional · string

    Start of the window entered, left, moves and completed count in. Defaults to 30 days before until.

  • untilquery · optional · string

    The instant open is taken at. Defaults to now.

  • tagquery · optional · array

    Measures only tasks carrying any of these tags.

  • group_byquery · optional · string

    on: also answer groups, the same rows per holder whose answer holds the work, a user_… or team_…, then null for an external wait on nobody.

    One of: on.

Responses

200The project's time in state
400The query string does not match the operation's schema
404No such task, or a `project` naming one this caller is not a member of

Generated from the spec this operation is implemented against, so the two names above cannot disagree with the surface a client sees.