--- title: "Change an issue's state" method: POST path: "/v1/issues/{idOrNumber}/transitions" tags: ["Issues"] --- # Change an issue's state `POST /v1/issues/{idOrNumber}/transitions` ## Request - Base URL: `https://docs.grepr.ai` (the document declares no server; this is the origin it was published from) - URL: `https://docs.grepr.ai/v1/issues/{idOrNumber}/transitions` - Auth: one of: - API key in header `GREPR-API-KEY` - OpenID Connect (`https://grepr-prod.us.auth0.com/.well-known/openid-configuration`) Moves an issue through its lifecycle: Triage, Ready, In progress, Waiting, Monitoring, Closed. Closing needs a resolution; Monitoring needs a revisit time or expiry; both need every assignee done unless a person forces it. ## Path parameters - `idOrNumber` string, required ## Request body - TransitionIssueRequest: Moves an issue to another state, checked against the state machine. - `comment` string: A comment posted with the transition, in the same transaction; required, with new evidence, when an agent reopens a `NOT_A_PROBLEM` issue. - `duplicateOf` string: The surviving issue's id or number; required exactly when `resolution` is `DUPLICATE`. - `evidence` IssueEvidence[]: Evidence added to the issue with the transition. - `from` string, date-time: Start of a log query's time range, or null. - `kind` 'LOG_QUERY' | 'EVENT' | 'URL', required: What the evidence points at. - `label` string: A short description of what it shows, or null. - `target` string, required: The Grepr log query for LOG_QUERY, the event id for EVENT, or an http(s) URL for URL. - `to` string, date-time: End of a log query's time range, or null. - `force` boolean: Lets a person move to Monitoring or Closed while assignees are still active; people only. - `guidance` boolean: Makes `comment` a guidance comment, which agents weigh; people only, so closing as `IGNORED` with guidance is one call. - `resolution` 'FIXED' | 'DUPLICATE' | 'NOT_A_PROBLEM' | 'IGNORED' | 'OBSOLETE' | 'EXPIRED': Why it closes; required when `to` is `CLOSED`, absent otherwise. - `to` 'TRIAGE' | 'READY' | 'IN_PROGRESS' | 'WAITING' | 'MONITORING' | 'CLOSED', required: The target state. Moving an open issue to the state it is already in changes no state but still applies `comment` and `evidence`; it rejects `resolution`, `duplicateOf` and `force`, which need a state change. - `version` integer: The version the transition was decided against, or null to apply it to whatever is current. ## Response `200` Issue transitioned - Issue: One durable problem or task on the organization's issue board. - `closedAt` string, date-time: When it closed, or null while open. - `confidence` 'CONFIRMED' | 'LIKELY' | 'UNVERIFIED': How sure the reporter is that the problem is real. - `createdAt` string, date-time: When it was filed. - `description` string: The current understanding, in markdown, kept current rather than appended to. - `duplicateOf` string: The surviving issue, set exactly when resolved as `DUPLICATE`; null in a response when the reader can't see the survivor. - `duplicateOfHidden` boolean: True in a response whose reader can't see the surviving issue. - `entities` object: The `entity:*` tags it concerns, the same vocabulary as memory tags, keys in lower case, sorted by key. - `evidence` IssueEvidence[]: Things a person can open to check the claim. - `from` string, date-time: Start of a log query's time range, or null. - `kind` 'LOG_QUERY' | 'EVENT' | 'URL', required: What the evidence points at. - `label` string: A short description of what it shows, or null. - `target` string, required: The Grepr log query for LOG_QUERY, the event id for EVENT, or an http(s) URL for URL. - `to` string, date-time: End of a log query's time range, or null. - `expiresAt` string, date-time: When the issue stops applying and closes as `EXPIRED`, or null. - `fingerprint` string: An optional free-form key for exact-match search, or null. - `firstSeenAt` string, date-time: The first sighting, or null before any. - `id` string: The issue id. - `labels` string[]: Categories, such as `cost`, sorted. - `lastSeenAt` string, date-time: The latest sighting, or when it was filed. - `links` IssueLink[]: Related pipelines, investigations, memories, suggestions and external tickets. - `hidden` boolean, nullable: True for a link to an issue the reader can't see. Set only in responses. - `kind` 'PIPELINE' | 'INVESTIGATION' | 'MEMORY' | 'AGENT_SUGGESTION' | 'EXTERNAL' | 'ISSUE', required: What the link points at. - `label` string: A short description, or null. - `target` string, nullable: Null only for a hidden issue link in a response. - `locks` IssueLocks: The fields and labels people have locked against agent changes. `state` never locks. - `fields` object: The locked fields, each with who locked it and when. - `labels` object: The locked labels, keyed by label. - `nextStep` string: The concrete next action and who it waits on, or null. - `number` integer: The short per-organization handle, shown as `#142`. - `occurrenceCount` integer: How many investigations sighted it. - `priority` 'P0' | 'P1' | 'P2' | 'P3': How soon someone should act. - `regressed` boolean: Whether it reopened on a new sighting after being fixed; cleared on its next close. - `reporter` IssueActor: Who made a change to an issue. An agent is named by its own id and the investigation it acted in, never by the service account it authenticated as, since several agents may share one. - `agentId` string: The agent, for an agent actor; null otherwise. - `id` string: The person's user id, the agent's execution principal (its service account's token subject), or `system` for the server. - `investigationId` string: The investigation the agent acted in, for an agent actor; null otherwise. - `kind` 'PERSON' | 'AGENT' | 'SYSTEM': A person, an agent, or the server. - `resolution` 'FIXED' | 'DUPLICATE' | 'NOT_A_PROBLEM' | 'IGNORED' | 'OBSOLETE' | 'EXPIRED': Why it closed; set exactly when `state` is `CLOSED`. - `revisitAt` string, date-time: When someone should check back, or null. Then a Monitoring issue's watcher is started on it, or, with no watcher, it goes back to `READY`. - `state` 'TRIAGE' | 'READY' | 'IN_PROGRESS' | 'WAITING' | 'MONITORING' | 'CLOSED': Where the issue is in its lifecycle. - `stateChangedAt` string, date-time: When the state last changed. - `teamIds` string[]: The teams that may see the issue, sorted. - `title` string: One line naming the problem. - `updatedAt` string, date-time: When it last changed. - `version` integer: Bumped by every change to a field, the state, an assignment, a lock or the teams. - `watchedBy` string: The agent watching it in `MONITORING`: the one that moved it there, started on it again when a sighting comes in or its revisit time passes. Null outside Monitoring. ## Other responses - `400`: The state machine does not allow the transition - `401`: Unauthorized - `403`: No permission, or a transition reserved for people - `404`: Issue not found - `409`: Stale version, active assignees, or an expired issue --- [API](https://skmtc.dev/grepr/apis/grepr-api.md) - [All operations](https://skmtc.dev/grepr/apis/grepr-api/llms.txt) - [OpenAPI document](https://skmtc.dev/grepr/apis/grepr-api/revisions/2a5ce03a0bf0?raw)