---
title: IssuesUpdateInput input | Wartiva GraphQL API
description: Input for the issueUpdate mutation. Wartiva GraphQL API reference with arguments, fields, and examples. Browse related operations and types.
url: https://wartiva.com/api-docs/types/issues-update-input.html
updated: 2026-10-07
---

Policies and findings · GraphQL input

# `IssuesUpdateInput` input

Input for the issueUpdate mutation.

## Fields

| Input Field | Description |
|---|---|
| `issueId` - [`ID!`](https://wartiva.com/api-docs/types/id.html) | Identifier of the issue to update: the [Issue](https://wartiva.com/api-docs/types/issue.html)'s `id`, the same value [issue](https://wartiva.com/api-docs/queries/issue.html) accepts. |
| `status` - [`IssueUpdateStatus!`](https://wartiva.com/api-docs/types/issue-update-status.html) | The desired new status. |
| `notes` - [`String`](https://wartiva.com/api-docs/types/string.html) | Optional user-authored notes to store on the issue. When omitted for a same-status update, notes are left unchanged (no-op). When provided, notes are updated regardless of the status transition. |
| `ignored` - [`IssueIgnoredInput`](https://wartiva.com/api-docs/types/issue-ignored-input.html) | Required when status is IGNORED. |

## Related types

- [`Issue`](https://wartiva.com/api-docs/types/issue.html) The triage record for a policy violation: a security concern on one graph object that needs remediation or a decision.

## Example

### Example

```json
{
  "issueId": "4",
  "status": "OPEN",
  "notes": "xyz789",
  "ignored": IssueIgnoredInput
}

```

---

Wartiva is in early access. Request access: https://wartiva.com/early-access.html  
All pages: https://wartiva.com/llms.txt