jira_put
Replace entire Jira resources like issues or projects with full updates using PUT requests. Specify API path and JSON body to modify data.
Instructions
Replace Jira resources (full update). Returns TOON format by default.
IMPORTANT - Cost Optimization: Use jq param to extract only needed fields from response
Output format: TOON (default) or JSON (outputFormat: "json")
Common operations:
Update issue (full):
/rest/api/3/issue/{issueIdOrKey}body:{"fields": {"summary": "New title", "description": {...}, "assignee": {"accountId": "..."}}}Update project:
/rest/api/3/project/{projectIdOrKey}body:{"name": "New Project Name", "description": "Updated description"}Set issue property:
/rest/api/3/issue/{issueIdOrKey}/properties/{propertyKey}body:{"value": "property value"}
Note: PUT replaces the entire resource. For partial updates, prefer PATCH.
API reference: https://developer.atlassian.com/cloud/jira/platform/rest/v3/
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | The Jira API endpoint path (without base URL). Must start with "/". Examples: "/rest/api/3/project", "/rest/api/3/search/jql", "/rest/api/3/issue/{issueIdOrKey}" | |
| queryParams | No | Optional query parameters as key-value pairs. Examples: {"maxResults": "50", "startAt": "0", "jql": "project=PROJ", "fields": "summary,status"} | |
| jq | No | JMESPath expression to filter/transform the response. IMPORTANT: Always use this to extract only needed fields and reduce token costs. Examples: "issues[*].{key: key, summary: fields.summary}" (extract specific fields), "issues[0]" (first result), "issues[*].key" (keys only). See https://jmespath.org | |
| outputFormat | No | Output format: "toon" (default, 30-60% fewer tokens) or "json". TOON is optimized for LLMs with tabular arrays and minimal syntax. | |
| body | Yes | Request body as a JSON object. Structure depends on the endpoint. Example for issue: {"fields": {"project": {"key": "PROJ"}, "summary": "Issue title", "issuetype": {"name": "Task"}}} |