# CreateIssueRequest

Files a new issue. Creating never deduplicates: search first, and update or record an occurrence on an existing issue instead of filing a second one. The reporter, number and timestamps come from the caller and the server, never from the request.

**Type**: `object`

## Properties

- name: confidence (required)
  type: enum: `CONFIRMED`, `LIKELY`, `UNVERIFIED`
  description: How sure the reporter is that the problem is real.

- name: description (optional)
  type: string
  description: The current understanding, in markdown, or null for none.

- name: entities (optional)
  type: object
  description: The `entity:*` tags it concerns; an unprefixed key is put in the `entity:` namespace.

- name: evidence (optional)
  type: array of `IssueEvidence`
  description: Things a person can open to check the claim.

- name: expiresAt (optional)
  type: string
  description: When the issue stops applying.

- name: fingerprint (optional)
  type: string
  description: An optional free-form key for exact-match search.

- name: labels (optional)
  type: array of string
  description: Categories; reuse the labels search reports as in use.

- name: links (optional)
  type: array of `IssueLink`
  description: Related pipelines, investigations, memories, suggestions and external tickets.

- name: nextStep (optional)
  type: string
  description: The concrete next action and who it waits on.

- name: priority (optional)
  type: enum: `P0`, `P1`, `P2`, `P3`
  description: How soon someone should act; agents must set it. A person who leaves it null files at `P2`, unlocked, so triage can set it.

- name: revisitAt (optional)
  type: string
  description: When someone should check back.

- name: state (optional)
  type: enum: `TRIAGE`, `READY`, `IN_PROGRESS`, `WAITING`, `MONITORING`, `CLOSED`
  description: The open state to file it in; null files it in `TRIAGE`. Agents may file only in `TRIAGE`, or `READY` when their handoff mode allows it.

- name: teamIds (optional)
  type: array of string
  description: The teams that may see it; people only, from the teams they can edit issues of (any for an organization-wide person). Absent: a team-scoped person's own teams, and none for an organization-wide person, which keeps the issue to organization-wide users.

- name: title (required)
  type: string
  description: One line naming the problem, not the symptom's timestamp.