Skip to main content

AvailabilityQueries

No description

type AvailabilityQueries {
availability(
webUserId: Long!
): UserAvailability
availabilitySummaries(
webUserId: Long!
): [ProcessAvailabilitySummary!]
planReassignment(
webUserId: Long!
processId: Long
method: String
): ReassignPlan
availabilityIntervals(
webUserIds: [Long!]!
from: String!
to: String!
timezone: String!
): [UserAvailabilityIntervals!]
myWorkSummary: MyWorkSummary
}

Fields

AvailabilityQueries.availability ● UserAvailability object

A user's availability state: global switch plus stored per-process deviations (absent = accepting)

AvailabilityQueries.availability.webUserId ● Long! non-null scalar

AvailabilityQueries.availabilitySummaries ● [ProcessAvailabilitySummary!] list object

Per-process control-panel summaries for a user, with bounded pending/covering counts

AvailabilityQueries.availabilitySummaries.webUserId ● Long! non-null scalar

AvailabilityQueries.planReassignment ● ReassignPlan object

Dry-run reassignment preview: classify a user's open tasks (all processes, or one) as movable, no-teammate-accepting or directly-assigned, with the picked recipient per movable task (method defaults to LeastWork; pass the method you will apply with). Nothing moves.

AvailabilityQueries.planReassignment.webUserId ● Long! non-null scalar
AvailabilityQueries.planReassignment.processId ● Long scalar
AvailabilityQueries.planReassignment.method ● String scalar

AvailabilityQueries.availabilityIntervals ● [UserAvailabilityIntervals!] list object

Actual availability intervals per user for an ISO date range in the given timezone, replayed from the availability event log; the right edge is clamped at now (the future belongs to schedule rules)

AvailabilityQueries.availabilityIntervals.webUserIds ● [Long!]! non-null scalar
AvailabilityQueries.availabilityIntervals.from ● String! non-null scalar
AvailabilityQueries.availabilityIntervals.to ● String! non-null scalar
AvailabilityQueries.availabilityIntervals.timezone ● String! non-null scalar

AvailabilityQueries.myWorkSummary ● MyWorkSummary object

The signed-in user's own at-a-glance state for the header chips: global switch, how many processes they are accepting out of the org total, and how many pending tasks are assigned to them. Cheap enough to refresh often; use availabilitySummaries for the full per-process panel.

Returned By

availability query