ArchAstro. V1. Teams. Tasks
(archastro v0.2.0)
Copy Markdown
TeamTask API resource.
Summary
Functions
List task blocker cycles
Create a task for an owner
List an owner's tasks
Get task activity metrics for a team
Functions
blocker_cycles(client, team, params \\ %ArchAstro.Types.Operations.GetApiV1TeamsTeamTasksBlockerCycles.Params{})
@spec blocker_cycles( ArchAstro.Client.t(), String.t(), ArchAstro.Types.Operations.GetApiV1TeamsTeamTasksBlockerCycles.Params.t() ) :: {:ok, ArchAstro.Types.Operations.GetApiV1TeamsTeamTasksBlockerCycles.Response.t()} | {:error, ArchAstro.Error.reason()}
List task blocker cycles
Runs an on-demand diagnostic over unfinished tasks owned by the specified team or user and returns a forward cursor-paginated page of complete cyclic blocker components. Detection is bounded to owners with at most 100 unfinished tasks. This endpoint is read-only: cycles do not prevent task updates, lease acquisition, or completion.
Successful response
@spec create( ArchAstro.Client.t(), String.t(), ArchAstro.Types.Operations.PostApiV1TeamsTeamTasks.Input.t() ) :: {:ok, ArchAstro.Types.Task.t()} | {:error, ArchAstro.Error.reason()}
Create a task for an owner
Creates a new task owned by the specified user or team and returns the full
task object. User-authenticated calls are attributed to the authenticated
user or agent. App-scoped developer and server-to-server callers must provide
the task's explicit org scope and an explicit user or agent actor for
team tasks; a user-owned task reuses the user in the route unless an explicit
agent is supplied. Every referenced principal is validated against the app,
owner, and team membership before creation.
The newly created task.
@spec list( ArchAstro.Client.t(), String.t(), ArchAstro.Types.Operations.GetApiV1TeamsTeamTasks.Params.t() ) :: {:ok, ArchAstro.Types.Operations.GetApiV1TeamsTeamTasks.Response.t()} | {:error, ArchAstro.Error.reason()}
List an owner's tasks
Returns tasks owned by the specified user or team. You can narrow results using the
optional filters below. By default results are returned in reverse chronological
order (most recently created first); use sort and order to sort by due date or
priority instead.
User-authenticated callers may list their personal tasks or tasks for teams they
have joined. Privileged callers provide the owner in the route; the owner's
organization is implied by that principal. An explicit org is optional and,
when set, must match the owner's organization.
Successful response
@spec metrics( ArchAstro.Client.t(), String.t(), ArchAstro.Types.Operations.GetApiV1TeamsTeamTasksMetrics.Params.t() ) :: {:ok, ArchAstro.Types.Operations.GetApiV1TeamsTeamTasksMetrics.Response.t()} | {:error, ArchAstro.Error.reason()}
Get task activity metrics for a team
Returns task activity metrics scoped to one team (the Network in ArchAgents).
open counts currently open or in-progress team tasks, created counts
tasks inserted in the UTC-day window, and completed counts tasks whose
closed_at falls in that window while still in a closed status. Hard-deleted
tasks are absent from the projection and therefore omitted. The daily series
is zero-filled across the requested window and includes reconstructed
end-of-day open stock (from remaining projection rows' inserted_at/closed_at).
Any authenticated team member may read this count-only Network summary. Requests from callers without team access return 404 so team existence is not disclosed.
Successful response
@spec search( ArchAstro.Client.t(), String.t(), ArchAstro.Types.Operations.GetApiV1TeamsTeamTasksSearch.Params.t() ) :: {:ok, ArchAstro.Types.Operations.GetApiV1TeamsTeamTasksSearch.Response.t()} | {:error, ArchAstro.Error.reason()}
Search an owner's tasks
Performs a full-text search over tasks owned by the specified user or team and returns
matching results. Combine q with the optional filters to narrow the result set
further. When no query is provided, the endpoint behaves like a filtered list.
The query field in the response echoes the effective search query.
User-authenticated callers may search their personal tasks or tasks for teams
they have joined. Privileged callers provide the owner in the route; the owner's
organization is implied by that principal. An explicit org is optional and,
when set, must match the owner's organization.
Successful response