Get Org Cues Issue Flow
Daily raised/resolved cues with the end-of-day open backlog, over [start, end] inclusive.
Each point is {date, raised, resolved, open}: raised and resolved count the cues that
opened and closed that day, and open is the backlog standing at the day’s end. The series
holds open(day) = open(day-1) + raised - resolved; cues opened before start are not
attributed to day one but form the opening backlog the first day starts from.
Derived from each persisted cue’s projection: a cue is raised once at created_at and, when
currently done, resolved once at its final status transition. Reopening continues the same issue
rather than counting another new one. A discarded cue counts as resolved — an operator
write-off has left the backlog just as a genuine resolution has — and so does an operator’s
resolution, which is a close like any other. Days are UTC calendar days. The
range spans at most MAX_ISSUE_FLOW_SPAN_DAYS days — one point per day, so an unbounded range
would build an unbounded response.
The org’s existence is already guaranteed by organization_access_required (the token’s member
must belong to org_id), so no separate lookup is needed.
Authorizations
The access token received from the authorization server in the OAuth 2.0 flow.
Path Parameters
The organization ID of the user's organization
Query Parameters
First day of the series (inclusive), UTC
Last day of the series (inclusive), UTC
