Jira Edit Issue

Updates an existing Jira issue with field values and operations. Supports direct field parameters (summary, description, assignee, priority, etc.) that are merged with the fields parameter. Direct parameters take precedence.

Precio

Action gratuita

Pago unificado

No compatible actualmente

• fieldsstring
  JSON string of fields for direct updates (e.g., summary, description). When including assignee in this object, you may provide either: (a) an accountId object '{"assignee": {"accountId": "<id>"}}', (b) a string email/display name '{"assignee": "user@example.com"}' or '{"assignee…
• labelsarray
  List of labels to set for the issue (replaces existing labels). New labels are created if they don't exist.
• updatestring
  JSON string for granular field operations (e.g., adding/removing labels, modifying list items). See Jira documentation for operation structure.
• summarystring
  Brief, descriptive title for the issue.
• assigneestring
  User to assign the issue to. Can be either an account ID (e.g., '5b10a2844c20165700ede21g') or name/email (e.g., 'john@company.com', 'John Doe'). When user email visibility is restricted, account ID is required. The system will auto-detect the type and search accordingly. Provid…
• due_datestring
  Expected resolution date in YYYY-MM-DD format. Use null to remove due date.
• descriptionstring
  Detailed description of the issue. Supports Markdown formatting including **bold**, *italic*, `code`, links [text](url), and lists. Note: Jira enforces size limits on the description field (typically ~32,767 characters, varies by instance). For very large content, consider split…
• notify_usersboolean
  If true, sends notification email to watchers. Setting to `False` requires admin or project admin permissions.
• return_issueboolean
  If true, response includes full updated issue details; if false, response is minimal.
• issue_id_or_keystring

  Obligatorio
  ID or key of the Jira issue to be edited.
• sprint_id_or_namestring
  Sprint to assign this issue to. Can be either a sprint ID (e.g., '123', '456') or sprint name (e.g., 'Sprint 1', 'Release Sprint'). The sprint must exist and be accessible. Use JIRA_LIST_SPRINTS to find available sprints.
• priority_id_or_namestring
  Priority level for the issue. Can be either a priority ID (e.g., '1', '2') or priority name (e.g., 'High', 'Medium', 'Low').

• data

  Obligatorio
  Data from the action execution
• errorstring
  Error if any occurred during the execution of the action
• successfulboolean

  Obligatorio
  Whether or not the action execution was successful or not

Aún no hay casos de uso relacionados verificados.