---
title: "Join an issue"
method: POST
path: "/v1/issues/{idOrNumber}/assignees"
tags: ["Issues"]
---

# Join an issue

`POST /v1/issues/{idOrNumber}/assignees`

## 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}/assignees`
- Auth: one of:
  - API key in header `GREPR-API-KEY`
  - OpenID Connect (`https://grepr-prod.us.auth0.com/.well-known/openid-configuration`)

Adds the caller as an active assignee. Joining a Ready issue moves it to In progress; joining again changes nothing, or reactivates a finished assignment.

## Path parameters

- `idOrNumber` string, required

## Request body

- JoinIssueRequest: Joins an issue as an active assignee: an agent as itself, a person as themselves. Joining a Ready issue moves it to In progress; joining again after finishing makes the assignment active again.
  - `note` string: What the caller will do, or null.
  - `version` integer: The version the join was decided against, or null for whatever is current.

## Response `200`

Joined

- IssueAssignees: An issue after a change to its assignees, with all of them.
  - `assignments` IssueAssignment[]: Its assignees, oldest first.
    - `assignedBy` 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.
    - `assigneeDeleted` boolean: Whether the assignee is an agent that has since been deleted; its assignment no longer keeps the issue out of Monitoring or Closed.
    - `assigneeId` string: The person's user id or the agent's id.
    - `assigneeKind` 'PERSON' | 'AGENT': A person or an agent.
    - `createdAt` string, date-time: When it was made.
    - `investigationId` string: For an agent's assignment, the run that made it active, which it ends with; null for a person's.
    - `note` string: A short note on its part, or null.
    - `status` 'ACTIVE' | 'DONE': Whether the assignee is still working on its part.
    - `updatedAt` string, date-time: When it last changed.
  - `issue` 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 issue is closed
- `401`: Unauthorized
- `403`: No permission to edit the issue
- `404`: Issue not found
- `409`: Stale version; the body carries the current 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)
