Usa Jira Edit Issue con Jira Tools mediante Aident Loadout. Revisa sus entradas, salidas, configuración, precio y riesgo antes de ejecutarla.
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.
fieldsstringJSON 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…
labelsarrayList of labels to set for the issue (replaces existing labels). New labels are created if they don't exist.
updatestringJSON string for granular field operations (e.g., adding/removing labels, modifying list items). See Jira documentation for operation structure.
summarystringBrief, descriptive title for the issue.
assigneestringUser 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_datestringExpected resolution date in YYYY-MM-DD format. Use null to remove due date.
descriptionstringDetailed 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_usersbooleanIf true, sends notification email to watchers. Setting to `False` requires admin or project admin permissions.
return_issuebooleanIf true, response includes full updated issue details; if false, response is minimal.
issue_id_or_keyObligatoriostringID or key of the Jira issue to be edited.
sprint_id_or_namestringSprint 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_namestringPriority level for the issue. Can be either a priority ID (e.g., '1', '2') or priority name (e.g., 'High', 'Medium', 'Low').
dataObligatorioData from the action execution
errorstringError if any occurred during the execution of the action
successfulObligatoriobooleanWhether or not the action execution was successful or not
Conexión con clave de API. Nivel de riesgo 2 de 5.
Action gratuita