NAiOS IconNAiOS Logo
Contacto
Contacto

Suscríbete a la newsletter

Novedades de IA y de producto. Sin spam, puedes darte de baja cuando quieras.

Consejo: usa tu email de empresa para una respuesta más relevante.

Comprobando seguridad…
NAiOS Icon
NAiOS Logo

El primer integrador de IA para empresas reales. Conecta todas tus herramientas de IA de forma segura y escalable.

+34 695482054info@naios.netinfo@netretina.ai
LinkedInNAiOS AcademyNetretina.AiContact UsX

Plataforma

  • Características
  • Integraciones
  • Planes y precios

Empresa

  • Sobre nosotros
  • Blog
  • Contacto

Compliance

  • Reglamento Europeo de IA
  • Transparencia de IA

Legal

  • Aviso legal
  • Política de privacidad
  • Términos y condiciones
  • Política de cookies
  • Devoluciones

© 2026 NAiOS. Todos los derechos reservados.

Un producto de Netretina.Ai

    Volver al catálogo

    Jira

    jira

    A tool for bug tracking, issue tracking, and agile project management.

    Project ManagementTask ManagementWeb del proveedor
    Acciones
    46
    Triggers
    17
    Autenticación
    —
    OAuth gestionado
    Sí
    Información técnica: el detalle de parámetros, schemas y triggers de esta página está pensado para equipos de integración. Si solo necesitas saber si tu herramienta favorita está disponible, basta con ver la lista de acciones.

    Acciones disponibles (46)

    Cada acción es una operación que el agente puede ejecutar contra este conector. Haz clic en una acción para ver sus parámetros.

    Add AttachmentJIRA_ADD_ATTACHMENTAcción

    Uploads and attaches a file to a jira issue.

    Parámetros de entrada

    • issue_keystringObligatorio

      The ID or key of the Jira issue to which the attachment will be added.

    • file_to_uploadobjectObligatorio

      File to be attached to the Jira issue. Supports various formats including images, documents, and other file types.

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    Add CommentJIRA_ADD_COMMENTAcción

    Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.

    Parámetros de entrada

    • commentstringObligatorio

      The comment text. Supports Markdown formatting including **bold**, *italic*, `code`, links [text](url), lists, and @mentions.

    • issue_id_or_keystringObligatorio

      The ID or key of the issue to add the comment to.

    • visibility_typestring

      Specifies the type of visibility restriction for the comment. Valid values are 'group' or 'role'. If this field is used, `visibility_value` must also be provided.

    • visibility_valuestring

      Name of the group or role that can view the comment (required if visibility_type is set).

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    Add Watcher to IssueJIRA_ADD_WATCHER_TO_ISSUEAcción

    Adds a user to an issue's watcher list by account id.

    Parámetros de entrada

    • account_idstringObligatorio

      The Atlassian Account ID (accountId) of the user to be added as a watcher. Important: Usernames cannot be used due to Jira API privacy changes; the accountId is required.

    • issue_id_or_keystringObligatorio

      The ID (a numerical identifier, e.g., '10000') or key (a project-prefixed string, e.g., 'PROJ-123') of the Jira issue to which the watcher will be added.

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    Assign IssueJIRA_ASSIGN_ISSUEAcción

    Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.

    Parámetros de entrada

    • account_idstring

      The Atlassian Account ID of the user to assign the issue to. Use `'-1'` (as a string) to assign to the project's default assignee. Provide `None` (Python null, which translates to JSON null) or omit this field to unassign the issue. Takes precedence over assignee_name if provided.

    • assignee_namestring

      Name of the user to assign the issue to. Can be either an email address (e.g., 'john@company.com') or display name (e.g., 'John Doe'). The system will auto-detect the type and search accordingly. Ignored if account_id is also provided.

    • issue_id_or_keystringObligatorio

      The ID or key of the issue to be assigned.

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    Bulk Create IssuesJIRA_BULK_CREATE_ISSUEAcción

    Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.

    Parámetros de entrada

    • issuesobject[]Obligatorio

      List of issues to be created (1 to 50 per request). Each issue definition follows the same structure as the single create issue action.

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    Create IssueJIRA_CREATE_ISSUEAcción

    Creates a new jira issue (e.g., bug, task, story) in a specified project.

    Parámetros de entrada

    • labelsstring[]

      List of labels to categorize the issue; new labels are created if they don't exist.

    • summarystringObligatorio

      Brief, descriptive title for the issue.

    • assigneestring

      Account ID of the user to assign the issue to. If unspecified, the project's default assignee may be used. Takes precedence over assignee_name if both are provided.

    • due_datestring

      Expected resolution date in YYYY-MM-DD format.

    • prioritystring

      Priority level for the issue. Can be either a priority ID (e.g., '1', '2') or priority name (e.g., 'High', 'Medium', 'Low'). Only set if the priority field is available on the project's create screen.

    • reporterstring

      Account ID of the user reporting the issue. Defaults to the API request user if unspecified.

    • versionsstring[]

      List of IDs for versions affected by this issue; versions must exist in the project.

    • sprint_idinteger

      ID of the sprint to assign this issue to. The issue will be added to the specified sprint if provided.

    • componentsstring[]

      List of component IDs (e.g., '10000'); components must already exist in the project.

    • issue_typestring

      Type of the issue (e.g., 'Bug', 'Task'); must be a valid type name for the project and is case-sensitive. Defaults to 'Task'.

    • descriptionstring

      Detailed description of the issue. Supports Markdown formatting including **bold**, *italic*, `code`, links [text](url), and lists.

    • environmentstring

      Environment details. Supports Markdown formatting including **bold**, *italic*, `code`, links [text](url), and lists.

    • project_keystringObligatorio

      Key of the Jira project (e.g., 'PROJ').

    • fix_versionsstring[]

      List of IDs for versions where the issue is/will be fixed; versions must exist in the project.

    • assignee_namestring

      Name or email of the user to assign the issue to. Can be either an email address (e.g., 'john@company.com') or display name (e.g., 'John Doe'). The system will auto-detect the type and search accordingly. Ignored if assignee (account ID) is also provided.

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    Link IssuesJIRA_CREATE_ISSUE_LINKAcción

    Links two jira issues using a specified link type with optional comment.

    Parámetros de entrada

    • commentstring

      An optional textual comment to add to the created issue link, providing additional context.

    • link_typestringObligatorio

      The specific type of relationship to establish between the issues (e.g., 'Blocks', 'Relates to', 'Duplicates').

    • inward_issue_keystringObligatorio

      The key of the issue that initiates the link relationship (the 'source' issue). For example, if creating a 'Blocks' link from Issue A to Issue B, Issue A is the inward issue.

    • outward_issue_keystringObligatorio

      The key of the issue that is the target of the link relationship (the 'destination' issue). For example, if creating a 'Blocks' link from Issue A to Issue B, Issue B is the outward issue.

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    Create ProjectJIRA_CREATE_PROJECTAcción

    Creates a new jira project with required lead, template, and type configuration.

    Parámetros de entrada

    • keystringObligatorio

      Unique key for the project. Must be unique across all Jira projects.

    • urlstring

      Optional URL for the project, like a Confluence space link or external website.

    • namestringObligatorio

      Human-readable name for the project.

    • avatar_idinteger

      Optional ID of an existing avatar for the project.

    • category_idinteger

      Optional ID of an existing project category.

    • descriptionstring

      Optional detailed textual description of the project.

    • assignee_typestringenum

      Default assignee for new issues: 'PROJECT_LEAD' (assigns to project lead) or 'UNASSIGNED' (issues remain unassigned).

      PROJECT_LEADUNASSIGNED
    • lead_account_idstringObligatorio

      Atlassian Account ID (not username or email) of the project lead.

    • project_type_keystringObligatorioenum

      Type of project: 'business' for Jira Core type projects or 'software' for Jira Software type projects.

      businesssoftware
    • permission_schemeinteger

      Optional ID of an existing permission scheme.

    • notification_schemeinteger

      Optional ID of an existing notification scheme.

    • project_template_keystringObligatorio

      Key of the project template, compatible with 'project_type_key'. Consult Jira documentation for available template keys for the chosen project type and Jira version.

    • issue_security_schemeinteger

      Optional ID of an existing issue security scheme.

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    Create SprintJIRA_CREATE_SPRINTAcción

    Creates a new sprint on a jira board with optional start/end dates and goal.

    Parámetros de entrada

    • goalstring

      Primary objective or goal for the sprint.

    • namestringObligatorio

      Name for the new sprint.

    • end_datestring

      Intended end date and time for the sprint (ISO 8601 format).

    • start_datestring

      Intended start date and time for the sprint (ISO 8601 format).

    • origin_board_idintegerObligatorio

      Identifier of the Jira board for the new sprint.

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    Create VersionJIRA_CREATE_VERSIONAcción

    Creates a new version for releases or milestones in a jira project.

    Parámetros de entrada

    • namestringObligatorio

      Name for the new version. It is recommended that version names be unique within a project.

    • archivedboolean

      Indicates if the version is marked as archived.

    • releasedboolean

      Indicates if the version is marked as released.

    • projectIdintegerObligatorio

      Numeric ID of the Jira project to which this version will be added. The project must exist.

    • startDatestring

      Start date for work on the version (YYYY-MM-DD format).

    • descriptionstring

      Textual description for the version, providing more context about its purpose or content.

    • releaseDatestring

      Release date for the version (YYYY-MM-DD format). Relevant if the version is marked as released or has a planned release.

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    Delete CommentJIRA_DELETE_COMMENTAcción

    Deletes a specific comment from a jira issue using its id and the issue's id/key; requires user permission to delete comments on the issue.

    Parámetros de entrada

    • idstringObligatorio

      The unique identifier of the comment to be deleted (e.g., '10001').

    • issueIdOrKeystringObligatorio

      The ID (e.g., '10000') or key (e.g., 'PROJ-123') of the Jira issue from which the comment will be deleted.

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    Delete IssueJIRA_DELETE_ISSUEAcción

    Deletes a jira issue by its id or key.

    Parámetros de entrada

    • delete_subtasksboolean

      If true, the issue's subtasks are also deleted. If false and the issue has subtasks, the deletion will fail.

    • issue_id_or_keystringObligatorio

      The ID or key of the issue to delete.

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    Delete VersionJIRA_DELETE_VERSIONAcción

    Deletes a jira version and optionally reassigns its issues.

    Parámetros de entrada

    • version_idstringObligatorio

      The unique identifier of the version to be deleted.

    • move_fix_issues_tostring

      The ID of an alternative version to which issues with the deleted version as their fix version will be moved. If unspecified or null, these issues will remain unassigned from a fix version.

    • move_affected_issues_tostring

      The ID of an alternative version to which issues with the deleted version as their affected version will be moved. If unspecified or null, these issues will remain unassigned from an affected version.

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    Delete WorklogJIRA_DELETE_WORKLOGAcción

    Deletes a worklog from a jira issue with estimate adjustment options.

    Parámetros de entrada

    • worklog_idstringObligatorio

      The ID of the specific worklog entry to be deleted from the issue.

    • increase_bystring

      Amount to increase the remaining estimate if `adjust_estimate` is 'manual' (e.g., '1h 30m', '5d').

    • new_estimatestring

      Value for the new remaining estimate if `adjust_estimate` is 'new' (e.g., '2h', '3d 4h').

    • notify_usersboolean

      If users watching the issue should be notified by email about the worklog deletion.

    • adjust_estimatestring

      How to update the issue's remaining estimate: 'new' (set to `new_estimate`), 'leave' (unchanged), 'manual' (reduce by `increase_by`), or 'auto' (reduce by deleted worklog time).

    • issue_id_or_keystringObligatorio

      The ID or key of the Jira issue from which the worklog will be deleted.

    • override_editable_flagboolean

      If true, allows deletion of the worklog even if the issue is in a closed status, potentially bypassing workflow restrictions.

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    Edit IssueJIRA_EDIT_ISSUEAcción

    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.

    Parámetros de entrada

    • fieldsobject

      Dictionary of fields for direct updates (e.g., summary, description). See Jira's 'edit issue metadata' for available fields. Provide complex data as a JSON string. Use `update` for more complex operations like list modifications.

    • labelsstring[]

      List of labels to set for the issue (replaces existing labels). New labels are created if they don't exist.

    • updateobject

      Dictionary for granular field operations (e.g., adding/removing labels, modifying list items). See Jira documentation for operation structure. Provide complex data as a JSON string.

    • 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'). The system will auto-detect the type and search accordingly. Use null to unassign.

    • 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.

    • 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_keystringObligatorio

      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').

    • 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').

    • override_editable_flagboolean

      If true, bypasses editable flag restrictions. Requires admin permissions.

    • override_screen_securityboolean

      If true, bypasses screen security restrictions. Requires admin permissions.

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    Find UsersJIRA_FIND_USERSAcción

    Searches for jira users by email, display name, or username to find account ids; essential for assigning issues, adding watchers, and other user-related operations.

    Parámetros de entrada

    • querystring

      A query string that is matched against user attributes. This can be used to search by display name, email address, or username. For example, 'john@company.com' to find a user by email.

    • start_atinteger

      The 0-based index of the first item to return in the page of results. Used for pagination.

    • usernamestring

      The username to search for. This parameter is deprecated in newer Jira versions but may still work in some instances.

    • account_idstring

      The account ID to search for. Use this to get user details when you already have the account ID.

    • max_resultsinteger

      The maximum number of items to return per page. Defaults to 50. Maximum allowed is typically 1000.

    • include_activeboolean

      Whether to include active users in the search results. Defaults to true.

    • include_inactiveboolean

      Whether to include inactive users in the search results. Defaults to false.

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    Get All Issue Type SchemesJIRA_GET_ALL_ISSUE_TYPE_SCHEMESAcción

    Retrieves all jira issue type schemes with optional filtering and pagination.

    Parámetros de entrada

    • idinteger[]

      The list of issue type scheme IDs to filter results. Returns only schemes with these IDs.

    • start_atinteger

      The index of the first item to return in a page of results (page offset). Default is 0.

    • max_resultsinteger

      The maximum number of items to return per page. Default is 50, maximum is 100.

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    Get all projectsJIRA_GET_ALL_PROJECTSAcción

    Retrieves all visible projects using the modern paginated jira api with server-side filtering and pagination support.

    Parámetros de entrada

    • namestring

      DEPRECATED: Use 'query' parameter instead. The project name (or part of it) to filter the results. This will be mapped to the 'query' parameter.

    • querystring

      Filter the results using a query string. Projects with a name or key that contains the query string are returned. The search is case-insensitive.

    • actionstring

      Filter results by projects for which the user can: 'view' (default), 'browse', 'edit', or 'admin'.

    • expandstring

      A comma-separated list of entities to expand in the response for additional project details. Valid options include: `description` (to include the project description), `issueTypes` (to include all issue types associated with the project), `lead` (to include information about the project lead), and `projectKeys` (to include all project keys associated with the project).

    • statusstring[]

      EXPERIMENTAL. Filter results by project status. Valid values: 'live', 'archived', 'deleted'.

    • orderBystring

      Order the results by a field. Valid values: 'category', 'issueCount', 'key', 'lastIssueUpdatedTime', 'name', 'owner', 'archivedDate', 'deletedDate'. Prefix with '-' for descending order.

    • startAtinteger

      The index of the first item to return in a page of results (page offset). The base index is 0.

    • categoryIdinteger

      The ID of the project category to filter by.

    • maxResultsinteger

      The maximum number of projects to return per page. Maximum allowed value is 100.

    • propertiesstring[]

      A list of project property keys to include in the response for each project, allowing retrieval of custom project entity properties. For example, if a project has a property with key 'com.example.property', including this key here as part of the list will return its value. Provide as a list of strings, e.g., `['property1', 'property2']`.

    Parámetros de salida

    • dataobjectObligatorio

      Paginated project search results with metadata and project list

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    Get Issue StatusesJIRA_GET_ALL_STATUSESAcción

    Retrieves all available issue statuses from jira with details.

    Parámetros de entrada

    Sin parámetros.

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    Get All UsersJIRA_GET_ALL_USERSAcción

    Retrieves all users from the jira instance including active, inactive, and other user states with pagination support.

    Parámetros de entrada

    • start_atinteger

      The 0-based index of the first item to return in the page of results. Used for pagination to retrieve users in chunks.

    • max_resultsinteger

      The maximum number of items to return per page. Used for pagination. The Jira instance might have a default and/or maximum limit for this value.

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    Get CommentJIRA_GET_COMMENTAcción

    Retrieves a specific comment by id from a jira issue with optional expansions.

    Parámetros de entrada

    • expandstring

      Optional. Sections to expand, e.g., 'renderedBody' for HTML. See Jira API docs for other values.

    • comment_idstringObligatorio

      Unique ID of the comment to retrieve.

    • issue_id_or_keystringObligatorio

      ID or key of the Jira issue (e.g., '10000' or 'PROJ-123').

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    Get Current UserJIRA_GET_CURRENT_USERAcción

    Retrieves detailed information about the currently authenticated jira user.

    Parámetros de entrada

    • expandstring

      Comma-separated list of user properties to expand, e.g., 'groups', 'applicationRoles'.

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    Get IssueJIRA_GET_ISSUEAcción

    Retrieves a jira issue by id or key with customizable fields and expansions.

    Parámetros de entrada

    • expandstring

      A comma-separated string of issue entities to expand in the response, providing more details. Common expansions include 'renderedFields' (HTML content), 'changelog' (history), 'transitions' (available workflows), and 'operations' (available actions).

    • fieldsstring[]

      A list of field names or IDs to return for the issue. If omitted or empty, a default set of fields (often all fields or all navigable fields) is returned. For specific fields, provide a list like `["summary", "status"]`.

    • propertiesstring[]

      A list of issue property keys to include in the response. Issue properties are extra key-value data attached to an issue, often by apps. Example: `["jira.meta.data", "com.example.custom.info"]`.

    • fields_by_keysboolean

      If true, the strings in the `fields` parameter are interpreted as field keys (e.g., 'summary') instead of field IDs (e.g., 'customfield_10000'). Default is false (uses field IDs).

    • update_historyboolean

      If true, viewing the issue will add it to the user's 'Recently Viewed' issues list. Set to false to prevent this, which can be useful for automated processes. The default behavior (true or false) can be determined by Jira's system settings if not explicitly set.

    • issue_id_or_keystringObligatorio

      The ID (e.g., '10000') or key (e.g., 'PROJ-123') of the Jira issue to retrieve.

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    Get Issue Link TypesJIRA_GET_ISSUE_LINK_TYPESAcción

    Retrieves all configured issue link types from jira.

    Parámetros de entrada

    Sin parámetros.

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    Get Issue PropertyJIRA_GET_ISSUE_PROPERTYAcción

    Retrieves a custom property from a jira issue by key.

    Parámetros de entrada

    • property_keystringObligatorio

      The key of the issue property to retrieve. Property keys are often dot-separated, like 'com.example.property.key'.

    • issue_id_or_keystringObligatorio

      The ID (e.g., '10000') or key (e.g., 'TEST-123') of the Jira issue.

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    Get Issue ResolutionsJIRA_GET_ISSUE_RESOLUTIONSAcción

    Retrieves all available issue resolution types from jira.

    Parámetros de entrada

    Sin parámetros.

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    Get issue typesJIRA_GET_ISSUE_TYPESAcción

    Retrieves all jira issue types available to the user using the modern api v3 endpoint; results vary based on 'administer jira' global or 'browse projects' project permissions.

    Parámetros de entrada

    Sin parámetros.

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    Get Issue Type SchemeJIRA_GET_ISSUE_TYPE_SCHEMEAcción

    Gets a jira issue type scheme by id with all associated issue types.

    Parámetros de entrada

    • issue_type_scheme_idstringObligatorio

      The unique identifier (ID) of the Jira issue type scheme to be retrieved.

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    Get Issue WatchersJIRA_GET_ISSUE_WATCHERSAcción

    Retrieves users watching a jira issue for update notifications.

    Parámetros de entrada

    • start_atinteger

      The 0-based index of the first watcher to return in the paginated list. Use for pagination.

    • max_resultsinteger

      The maximum number of watchers to return per page. Use for pagination. Must be 1 or greater if provided.

    • issue_id_or_keystringObligatorio

      The ID or key of the Jira issue for which to retrieve watchers. This can be the numerical ID (e.g., '10000') or the human-readable key (e.g., 'PROJ-123').

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    Get Issue WorklogsJIRA_GET_ISSUE_WORKLOGSAcción

    Retrieves worklogs for a jira issue with user permission checks.

    Parámetros de entrada

    • start_atinteger

      Index of the first worklog to return (for pagination). Defaults to 0.

    • max_resultsinteger

      Maximum number of worklogs to return per page. Defaults to a system-defined limit.

    • started_afterinteger

      Filters worklogs to include only those started after this Unix timestamp (milliseconds).

    • started_beforeinteger

      Filters worklogs to include only those started before this Unix timestamp (milliseconds).

    • issue_id_or_keystringObligatorio

      The ID or key of the issue for which worklogs are to be fetched.

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    Get Project VersionsJIRA_GET_PROJECT_VERSIONSAcción

    Retrieves all versions for a jira project with optional expansion.

    Parámetros de entrada

    • expandstring

      Comma-separated string of properties to expand for each version (e.g., 'operations', 'issuesstatus').

    • project_id_or_keystringObligatorio

      The ID or unique key of the Jira project for which versions are to be retrieved. For example, '10000' or 'PROJECTKEY'.

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    Get Issue Remote LinksJIRA_GET_REMOTE_ISSUE_LINKSAcción

    Retrieves links from a jira issue to external resources.

    Parámetros de entrada

    • global_idstring

      Optional. The global ID of a specific remote issue link to retrieve, provided by the external linking application. If specified, only the remote issue link matching this global ID is returned.

    • issue_id_or_keystringObligatorio

      The ID (e.g., '10000') or key (e.g., 'PROJECT-123') of the Jira issue for which to retrieve remote links.

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    Get TransitionsJIRA_GET_TRANSITIONSAcción

    Retrieves available workflow transitions for a jira issue.

    Parámetros de entrada

    • expandstring

      A comma-separated list of properties to expand in the response. Use 'transitions.fields' to include the fields associated with each transition, providing details on what input is expected or allowed.

    • transition_idstring

      The ID of a specific transition to retrieve. If provided, only details for this transition are returned.

    • issue_id_or_keystringObligatorio

      The ID (e.g., '10000') or key (e.g., 'PROJ-123') of the Jira issue for which to retrieve transitions.

    • skip_remote_only_conditionboolean

      If true, conditions defined by remote apps that only run remotely will be skipped during evaluation.

    • sort_by_ops_bar_and_statusboolean

      If true, sorts the returned transitions by their order in the operations bar and then by status category.

    • include_unavailable_transitionsboolean

      If true, transitions that are not currently available for the issue (e.g., due to unmet conditions) will be included in the response.

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    Get Issue VotesJIRA_GET_VOTESAcción

    Fetches voting details for a jira issue; requires voting to be enabled in jira's general settings.

    Parámetros de entrada

    • issue_id_or_keystringObligatorio

      The ID or key of the Jira issue (e.g., 'PROJ-123' or '10000').

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    Get WorklogsJIRA_GET_WORKLOGAcción

    Retrieves worklogs for a specified jira issue.

    Parámetros de entrada

    • expandstring

      A comma-separated list of worklog properties to expand in the response. For instance, 'properties' can be used to include custom fields associated with the worklogs. Refer to the Jira API documentation for other possible values.

    • start_atinteger

      The 0-based index of the first worklog to return. Used for pagination to retrieve results beyond the initial page. For example, if `maxResults` is 50, `startAt=50` retrieves the second page.

    • max_resultsinteger

      The maximum number of worklogs to return per page. Used for pagination. If not specified, a Jira-defined default is used (e.g., 50).

    • started_afterinteger

      Filters worklogs to include only those started on or after this specified date and time. Provide as a Unix timestamp in milliseconds (milliseconds since January 1, 1970, 00:00:00 UTC).

    • started_beforeinteger

      Filters worklogs to include only those started on or before this specified date and time. Provide as a Unix timestamp in milliseconds (milliseconds since January 1, 1970, 00:00:00 UTC).

    • issue_id_or_keystringObligatorio

      The ID (e.g., '10001') or key (e.g., 'PROJECT-123') of the Jira issue for which to retrieve worklogs.

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    List BoardsJIRA_LIST_BOARDSAcción

    Retrieves paginated jira boards with filtering and sorting options.

    Parámetros de entrada

    • namestring

      Filters results to boards whose name contains the string (case-insensitive).

    • typestringenum

      Filters results to boards of the specified type.

      scrumkanban
    • orderBystring

      Field to order boards by (e.g., 'name', '-name' for descending). Refer to Jira API docs for all sortable fields.

    • start_atinteger

      Index of the first board to return (0-based) for pagination.

    • max_resultsinteger

      Maximum number of boards to return per page.

    • includePrivateboolean

      Include private boards in the results.

    • projectKeyOrIdstring

      Filters results to boards for the specified project, by its key (e.g., 'PROJECTKEY') or ID (e.g., '10000').

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    List Issue CommentsJIRA_LIST_ISSUE_COMMENTSAcción

    Retrieves paginated comments from a jira issue with optional ordering.

    Parámetros de entrada

    • expandstring

      Use 'renderedBody' to include the HTML-rendered version of the comment body in the response.

    • order_bystring

      Specifies the field to sort comments by; use 'created' for ascending by creation date (currently the only supported value).

    • start_atinteger

      The 0-based index of the first comment to return.

    • max_resultsinteger

      The maximum number of comments to return per page.

    • issue_id_or_keystringObligatorio

      The ID (e.g., '10000') or key (e.g., 'PROJ-123') of the Jira issue from which to retrieve comments.

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    List SprintsJIRA_LIST_SPRINTSAcción

    Retrieves paginated sprints from a jira board with optional state filtering.

    Parámetros de entrada

    • statestring

      Filters sprints by state: 'future', 'active', or 'closed'. Returns all states if omitted.

    • board_idintegerObligatorio

      Unique identifier of the Jira board.

    • start_atinteger

      0-based starting index for pagination.

    • max_resultsinteger

      Maximum number of sprints per page.

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    Move Issues to SprintJIRA_MOVE_ISSUE_TO_SPRINTAcción

    Moves one or more jira issues to a specified active sprint.

    Parámetros de entrada

    • issuesstring[]Obligatorio

      A list of issue keys (e.g., 'PROJ-123') to be moved to the specified sprint.

    • sprint_idintegerObligatorio

      Unique identifier for the target sprint.

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    Remove Watcher from IssueJIRA_REMOVE_WATCHER_FROM_ISSUEAcción

    Removes a user from an issue's watcher list by account id.

    Parámetros de entrada

    • account_idstringObligatorio

      The account ID of the user to remove from the issue's watchers list.

    • issue_id_or_keystringObligatorio

      The ID or key of the issue.

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    Search Issues Using JQL (GET)JIRA_SEARCH_FOR_ISSUES_USING_JQL_GETAcción

    Searches for jira issues using jql with pagination and field selection.

    Parámetros de entrada

    • jqlstringObligatorio

      Jira Query Language (JQL) string for searching issues.

    • expandstring

      Comma-separated list of entities to expand within issues (e.g., `renderedFields`, `changelog`).

    • fieldsstring[]

      Specific issue fields to retrieve (e.g., `summary`, `customfield_10010`, `*all`, `*navigable`). Defaults if omitted.

    • start_atinteger

      0-based index for the first issue in pagination.

    • propertiesstring[]

      List of issue property keys (key-value metadata) to retrieve.

    • max_resultsinteger

      Maximum issues to retrieve per page; Jira API may enforce limits.

    • fields_by_keysboolean

      Set to `True` to identify fields by keys (e.g., 'customfield_10000') instead of IDs.

    • validate_querystring

      Controls JQL query validation: `strict` (fails on invalid JQL), `warn` (warnings, empty result), `none` (no validation). `true` is an alias for `strict`, `false` for `none`.

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    Search Issues Using JQL (POST)JIRA_SEARCH_FOR_ISSUES_USING_JQL_POSTAcción

    Searches for jira issues using jql via post request for complex queries; ideal for lengthy jql queries that might exceed url character limits

    Parámetros de entrada

    • jqlstringObligatorio

      The JQL (Jira Query Language) query string to use for the search. For example, 'project = HSP AND issuetype = Bug'.

    • expandstring

      A comma-separated list of entities to expand in the response. Options include: 'renderedFields' (HTML values), 'names' (display name of fields), 'schema' (field type schema), 'transitions' (possible issue transitions), 'operations' (possible issue operations), 'editmeta' (field editability info), 'changelog' (recent updates), 'versionedRepresentations' (field version history).

    • fieldsstring[]

      A list of fields to return for each issue. By default, all fields are returned. Specify 'none' to return no fields. Examples: 'summary', 'status', 'assignee'. Use '*navigable' to return all navigable fields.

    • start_atinteger

      The 0-based index of the first issue to return from the query results. Used for pagination.

    • propertiesstring[]

      A list of issue property keys to return for each issue. Issue properties are key-value pairs on the issue that can be set and read by apps (e.g., 'jira.issue.tools', 'com.example.application:properties').

    • max_resultsinteger

      The maximum number of issues to return per page. Used for pagination.

    • fields_by_keysboolean

      If true, returns field values referenced by their keys (e.g., 'customfield_10000') instead of their IDs.

    • validate_querystring

      Controls how the JQL query is validated. 'strict' throws an error for invalid JQL. 'warn' returns a warning for invalid JQL but still executes the query if possible. 'none' performs no JQL validation.

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    Search issuesJIRA_SEARCH_ISSUESAcción

    Advanced jira issue search supporting structured filters and raw jql.

    Parámetros de entrada

    • jqlstring

      Raw JQL query for advanced users. Takes precedence over filters.

    • labelsstring[]

      Filter by labels (all labels must match).

    • assigneestring

      Filter by assignee. Can be account ID (e.g., '712020:abc...'), email (e.g., 'john@company.com'), display name (e.g., 'John Doe'), or 'unassigned'.

    • start_atinteger

      0-based index of the first issue to return (for pagination).

    • max_resultsinteger

      Maximum number of issues to return.

    • project_keystring

      Filter by project key (e.g., 'PROJ').

    • text_searchstring

      Search in summary and description text.

    • created_afterstring

      Filter issues created after this date. Supports YYYY-MM-DD format or relative dates like '-30m' (last 30 minutes), '-7d' (last 7 days), '-1w' (last week), '-1M' (last month).

    • updated_afterstring

      Filter issues updated after this date. Supports YYYY-MM-DD format or relative dates like '-30m' (last 30 minutes), '-7d' (last 7 days), '-1w' (last week), '-1M' (last month).

    • created_beforestring

      Filter issues created before this date (YYYY-MM-DD format).

    • updated_beforestring

      Filter issues updated before this date (YYYY-MM-DD format).

    • sprint_id_or_namestring

      Filter by sprint. Can be sprint ID (e.g., '123') or name (e.g., 'Sprint 1', 'Release Sprint').

    • status_id_or_namestring

      Filter by status. Can be either a status ID (e.g., '10001') or name (e.g., 'To Do', 'In Progress', 'Done').

    • priority_id_or_namestring

      Filter by priority. Can be either a priority ID (e.g., '1', '2') or name (e.g., 'High', 'Medium', 'Low').

    • issue_type_id_or_namestring

      Filter by issue type. Can be either an issue type ID (e.g., '10001') or name (e.g., 'Bug', 'Task', 'Story').

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    Send Notification for IssueJIRA_SEND_NOTIFICATION_FOR_ISSUEAcción

    Sends a customized email notification for a jira issue.

    Parámetros de entrada

    • toobjectObligatorio

      A `NotificationRecipients` object specifying who should receive the notification. At least one recipient category (e.g., reporter, assignee, a user, or a group) within this object must be configured.

    • subjectstringObligatorio

      The subject line for the email notification.

    • restrictobject

      Optional restrictions defining who can receive the notification. If specified, notifications are sent only to users who meet the criteria in `groups` (if provided) AND `permissions` (if provided), AND also have general permission to view the issue.

    • html_bodystring

      The HTML content of the email notification. This field is optional unless `restrict` is used, in which case it becomes mandatory. It is recommended to also provide `text_body` for email clients that do not support HTML.

    • text_bodystringObligatorio

      The plain text content of the email notification. This field is always mandatory.

    • issue_id_or_keystringObligatorio

      The ID (e.g., '10000') or key (e.g., 'PROJ-123') of the Jira issue for which the notification will be sent.

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    Transition IssueJIRA_TRANSITION_ISSUEAcción

    Transitions a jira issue to a different workflow state, with support for transition name lookup and user assignment by email.

    Parámetros de entrada

    • commentstring

      Optional comment to add during the transition. Supports Markdown formatting including **bold**, *italic*, `code`, links [text](url), and lists.

    • assigneestring

      Account ID of the user to assign the issue to during transition. Takes precedence over assignee_name.

    • resolutionstring

      Optional resolution to set (e.g., 'Done', 'Fixed', 'Won't Do').

    • assignee_namestring

      Name of the user to assign the issue to during transition. Can be either an email address (e.g., 'john@company.com') or display name (e.g., 'John Doe'). The system will auto-detect the type and search accordingly. Ignored if assignee (account ID) is provided.

    • issue_id_or_keystringObligatorio

      The ID or key of the issue to transition.

    • transition_id_or_namestringObligatorio

      The ID or name of the transition to apply.

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    Update CommentJIRA_UPDATE_COMMENTAcción

    Updates text content or visibility of an existing jira comment.

    Parámetros de entrada

    • comment_idstringObligatorio

      The unique ID of the comment to be updated.

    • comment_textstringObligatorio

      The new text content for the comment. This will replace the existing comment body. Supports plain text and basic formatting like *bold*, _italic_, and @mentions.

    • notify_usersboolean

      A boolean flag indicating whether to send notifications to users about the comment update. Defaults to True.

    • issue_id_or_keystringObligatorio

      The ID or key of the Jira issue where the comment is located. This can be the numerical ID or the project key followed by the issue number (e.g., 'PROJ-123').

    • visibility_typestring

      Optional. The type of visibility restriction to apply to the comment. If provided, `visibility_value` must also be specified. Valid values are 'group' or 'role'.

    • visibility_valuestring

      Optional. The name of the group or role to restrict comment visibility to. Required if `visibility_type` is specified. For 'group' type, provide the group name (e.g., 'jira-administrators'). For 'role' type, provide the project role name (e.g., 'Administrators').

    Parámetros de salida

    • dataobjectObligatorio

      Data from the action execution

    • errorstring

      Error if any occurred during the execution of the action

    • successfulbooleanObligatorio

      Whether or not the action execution was successful or not

    Triggers (17)

    Los triggers son eventos externos que pueden iniciar un flujo en tus agentes (ej: nuevo email, mensaje recibido, registro creado).

    Comment CreatedJIRA_COMMENT_CREATEDTrigger

    Triggers when a comment is posted on a Jira issue. Can deliver comments on issues the connected account cannot open in Jira itself.

    Configuración

    • assigneestring

      Only fire when the commented issue is assigned to this person, by Atlassian accountId. Use JIRA_FIND_USERS with query='<name or email>' and take 'account_id'. A comment on an unassigned issue matches nobody, so setting this excludes them. Leave unset to receive comments regardless of assignee.

    • comment_authorstring

      Only fire for comments written by this person, by Atlassian accountId. Use JIRA_FIND_USERS with query='<name or email>' and take 'account_id'. Leave unset to receive comments from anyone.

    • issue_typestring

      Only fire for comments on issues of this type, by name. Use JIRA_GET_ISSUE_TYPES to list the types configured on this site. Leave unset to receive comments on every issue type.

    • project_idintegerObligatorio

      The Jira project to watch, as its NUMERIC project id (e.g. 10705) and not the project key. Call JIRA_GET_ALL_PROJECTS with query='<your project key or name>' and take the 'id' off the result. Required: this trigger fires only for issues in this project, so create one trigger per project you want to watch.

    • statusstring

      Only fire when the commented issue is in this status, by name. Use JIRA_GET_ALL_STATUSES to list this site's statuses. Leave unset to receive comments whatever the issue's status.

    Payload del evento

    • commentobjectObligatorio

      The comment the event is about.

    • issueobjectObligatorio

      The issue the comment is on.

    Comment DeletedJIRA_COMMENT_DELETEDTrigger

    Triggers when a comment is deleted from a Jira issue. The deleted comment's text still arrives. Can deliver comments on issues the connected account cannot open in Jira itself.

    Configuración

    • assigneestring

      Only fire when the commented issue is assigned to this person, by Atlassian accountId. Use JIRA_FIND_USERS with query='<name or email>' and take 'account_id'. A comment on an unassigned issue matches nobody, so setting this excludes them. Leave unset to receive comments regardless of assignee.

    • comment_authorstring

      Only fire for comments written by this person, by Atlassian accountId. Use JIRA_FIND_USERS with query='<name or email>' and take 'account_id'. Leave unset to receive comments from anyone.

    • issue_typestring

      Only fire for comments on issues of this type, by name. Use JIRA_GET_ISSUE_TYPES to list the types configured on this site. Leave unset to receive comments on every issue type.

    • project_idintegerObligatorio

      The Jira project to watch, as its NUMERIC project id (e.g. 10705) and not the project key. Call JIRA_GET_ALL_PROJECTS with query='<your project key or name>' and take the 'id' off the result. Required: this trigger fires only for issues in this project, so create one trigger per project you want to watch.

    • statusstring

      Only fire when the commented issue is in this status, by name. Use JIRA_GET_ALL_STATUSES to list this site's statuses. Leave unset to receive comments whatever the issue's status.

    Payload del evento

    • commentobjectObligatorio

      The comment the event is about.

    • issueobjectObligatorio

      The issue the comment is on.

    Comment UpdatedJIRA_COMMENT_UPDATEDTrigger

    Triggers when an existing comment on a Jira issue is edited. The payload carries the comment as it now reads, not what it said before. Can deliver comments on issues the connected account cannot open in Jira itself.

    Configuración

    • assigneestring

      Only fire when the commented issue is assigned to this person, by Atlassian accountId. Use JIRA_FIND_USERS with query='<name or email>' and take 'account_id'. A comment on an unassigned issue matches nobody, so setting this excludes them. Leave unset to receive comments regardless of assignee.

    • comment_authorstring

      Only fire for comments written by this person, by Atlassian accountId. Use JIRA_FIND_USERS with query='<name or email>' and take 'account_id'. Leave unset to receive comments from anyone.

    • issue_typestring

      Only fire for comments on issues of this type, by name. Use JIRA_GET_ISSUE_TYPES to list the types configured on this site. Leave unset to receive comments on every issue type.

    • project_idintegerObligatorio

      The Jira project to watch, as its NUMERIC project id (e.g. 10705) and not the project key. Call JIRA_GET_ALL_PROJECTS with query='<your project key or name>' and take the 'id' off the result. Required: this trigger fires only for issues in this project, so create one trigger per project you want to watch.

    • statusstring

      Only fire when the commented issue is in this status, by name. Use JIRA_GET_ALL_STATUSES to list this site's statuses. Leave unset to receive comments whatever the issue's status.

    Payload del evento

    • commentobjectObligatorio

      The comment the event is about.

    • issueobjectObligatorio

      The issue the comment is on.

    Issue CreatedJIRA_ISSUE_CREATEDTrigger

    Triggers when an issue is created in Jira, including a sub-task. Can deliver issues the connected account cannot open in Jira itself.

    Configuración

    • assigneestring

      Only fire when the issue is assigned to this person, by Atlassian accountId. Use JIRA_FIND_USERS with query='<name or email>' and take 'account_id' — an accountId cannot be typed from memory. An unassigned issue matches nobody, so setting this excludes them. Leave unset to receive issues regardless of assignee.

    • issue_typestring

      Only fire for issues of this type, by name. Use JIRA_GET_ISSUE_TYPES to list the types configured on this site. Leave unset to receive every issue type.

    • project_idintegerObligatorio

      The Jira project to watch, as its NUMERIC project id (e.g. 10705) and not the project key. Call JIRA_GET_ALL_PROJECTS with query='<your project key or name>' and take the 'id' off the result. Required: this trigger fires only for issues in this project, so create one trigger per project you want to watch.

    • reporterstring

      Only fire when the issue was reported by this person, by Atlassian accountId. Use JIRA_FIND_USERS with query='<name or email>' and take 'account_id'. Leave unset to receive issues from any reporter.

    • statusstring

      Only fire when the issue's status is this, by name. Use JIRA_GET_ALL_STATUSES to list this site's statuses. Leave unset to receive issues in any status.

    Payload del evento

    • issueobjectObligatorio

      The issue the event is about.

    • userobjectObligatorio

      Whoever's action produced the event.

    Issue DeletedJIRA_ISSUE_DELETEDTrigger

    Triggers when an issue is deleted from Jira. The deleted issue's full field set still arrives, so the filters below apply to it as usual. Can deliver issues the connected account cannot open in Jira itself.

    Configuración

    • assigneestring

      Only fire when the issue is assigned to this person, by Atlassian accountId. Use JIRA_FIND_USERS with query='<name or email>' and take 'account_id' — an accountId cannot be typed from memory. An unassigned issue matches nobody, so setting this excludes them. Leave unset to receive issues regardless of assignee.

    • issue_typestring

      Only fire for issues of this type, by name. Use JIRA_GET_ISSUE_TYPES to list the types configured on this site. Leave unset to receive every issue type.

    • project_idintegerObligatorio

      The Jira project to watch, as its NUMERIC project id (e.g. 10705) and not the project key. Call JIRA_GET_ALL_PROJECTS with query='<your project key or name>' and take the 'id' off the result. Required: this trigger fires only for issues in this project, so create one trigger per project you want to watch.

    • reporterstring

      Only fire when the issue was reported by this person, by Atlassian accountId. Use JIRA_FIND_USERS with query='<name or email>' and take 'account_id'. Leave unset to receive issues from any reporter.

    • statusstring

      Only fire when the issue's status is this, by name. Use JIRA_GET_ALL_STATUSES to list this site's statuses. Leave unset to receive issues in any status.

    Payload del evento

    • issueobjectObligatorio

      The issue the event is about.

    • userobjectObligatorio

      Whoever's action produced the event.

    Issue UpdatedJIRA_ISSUE_UPDATEDTrigger

    Triggers when a field on an existing issue changes — its status, assignee, or anything else on the issue. One edit can change several fields and arrives as one event; creating a sub-task also updates its parent. Commenting does not fire it. Can deliver issues the connected account cannot open in Jira itself.

    Configuración

    • assigneestring

      Only fire when the issue is assigned to this person, by Atlassian accountId. Use JIRA_FIND_USERS with query='<name or email>' and take 'account_id' — an accountId cannot be typed from memory. An unassigned issue matches nobody, so setting this excludes them. Leave unset to receive issues regardless of assignee.

    • changed_fieldstring

      Only fire when this field is among the fields that changed, by field id — 'status', 'assignee', 'priority', 'summary', 'labels', 'duedate', 'description', 'resolution'. One edit can change several fields at once and the trigger fires if any of them matches. A custom field uses its id ('customfield_10020'); find it with JIRA_GET_FIELDS. Leave unset to fire on any change.

    • issue_typestring

      Only fire for issues of this type, by name. Use JIRA_GET_ISSUE_TYPES to list the types configured on this site. Leave unset to receive every issue type.

    • project_idintegerObligatorio

      The Jira project to watch, as its NUMERIC project id (e.g. 10705) and not the project key. Call JIRA_GET_ALL_PROJECTS with query='<your project key or name>' and take the 'id' off the result. Required: this trigger fires only for issues in this project, so create one trigger per project you want to watch.

    • reporterstring

      Only fire when the issue was reported by this person, by Atlassian accountId. Use JIRA_FIND_USERS with query='<name or email>' and take 'account_id'. Leave unset to receive issues from any reporter.

    • statusstring

      Only fire when the issue's status is this, by name. Use JIRA_GET_ALL_STATUSES to list this site's statuses. Leave unset to receive issues in any status.

    Payload del evento

    • changelogobjectObligatorio

      What the edit changed.

    • issueobjectObligatorio

      The issue the event is about.

    • userobjectObligatorio

      Whoever's action produced the event.

    Sprint ClosedJIRA_SPRINT_CLOSEDTrigger

    Triggers when a sprint is completed and moves into the closed state.

    Configuración

    • board_idinteger

      Only fire for sprints belonging to this board, by numeric board id. A sprint event carries no project, so the board is the only way to narrow it; use JIRA_LIST_BOARDS to find the id. Leave unset to receive sprint events from every board on the site.

    Payload del evento

    • sprintobjectObligatorio

      The sprint the event is about.

    Sprint CreatedJIRA_SPRINT_CREATEDTrigger

    Triggers when a sprint is created on a Jira board. Creating a sprint does not start it — watch Sprint Started for that.

    Configuración

    • board_idinteger

      Only fire for sprints belonging to this board, by numeric board id. A sprint event carries no project, so the board is the only way to narrow it; use JIRA_LIST_BOARDS to find the id. Leave unset to receive sprint events from every board on the site.

    Payload del evento

    • sprintobjectObligatorio

      The sprint the event is about.

    Sprint StartedJIRA_SPRINT_STARTEDTrigger

    Triggers when a sprint moves into the active state.

    Configuración

    • board_idinteger

      Only fire for sprints belonging to this board, by numeric board id. A sprint event carries no project, so the board is the only way to narrow it; use JIRA_LIST_BOARDS to find the id. Leave unset to receive sprint events from every board on the site.

    Payload del evento

    • sprintobjectObligatorio

      The sprint the event is about.

    Sprint UpdatedJIRA_SPRINT_UPDATEDTrigger

    Triggers when a sprint's name, goal, dates or state changes. Starting a sprint also fires this when the same call changed another field; closing one does not.

    Configuración

    • board_idinteger

      Only fire for sprints belonging to this board, by numeric board id. A sprint event carries no project, so the board is the only way to narrow it; use JIRA_LIST_BOARDS to find the id. Leave unset to receive sprint events from every board on the site.

    Payload del evento

    • oldValueobjectObligatorio

      The sprint as it was before the update.

    • sprintobjectObligatorio

      The sprint the event is about.

    Version CreatedJIRA_VERSION_CREATEDTrigger

    Triggers when a project version is created in Jira.

    Configuración

    • project_idinteger

      Only fire for versions in this Jira project, given as the NUMERIC project id (e.g. 10705). A version event carries only the id and never the project key. Call JIRA_GET_ALL_PROJECTS with query='<your project key or name>' and take the 'id' off the result. Leave unset to receive version events from every project on the site.

    Payload del evento

    • versionobjectObligatorio

      The version the event is about.

    Version DeletedJIRA_VERSION_DELETEDTrigger

    Triggers when a project version is deleted outright. A version that disappeared because it was merged into another one fires Version Merged instead.

    Configuración

    • project_idinteger

      Only fire for versions in this Jira project, given as the NUMERIC project id (e.g. 10705). A version event carries only the id and never the project key. Call JIRA_GET_ALL_PROJECTS with query='<your project key or name>' and take the 'id' off the result. Leave unset to receive version events from every project on the site.

    Payload del evento

    • versionobjectObligatorio

      The version the event is about.

    Version MergedJIRA_VERSION_MERGEDTrigger

    Triggers when a project version is merged into another one, carrying both the version that went away and the one that survived.

    Configuración

    • project_idinteger

      Only fire for versions in this Jira project, given as the NUMERIC project id (e.g. 10705). A version event carries only the id and never the project key. Call JIRA_GET_ALL_PROJECTS with query='<your project key or name>' and take the 'id' off the result. Leave unset to receive version events from every project on the site.

    Payload del evento

    • mergedToobjectObligatorio

      The version that survived the merge.

    • versionobjectObligatorio

      The version the event is about.

    Version MovedJIRA_VERSION_MOVEDTrigger

    Triggers when a project version is reordered within its project's release list.

    Configuración

    • project_idinteger

      Only fire for versions in this Jira project, given as the NUMERIC project id (e.g. 10705). A version event carries only the id and never the project key. Call JIRA_GET_ALL_PROJECTS with query='<your project key or name>' and take the 'id' off the result. Leave unset to receive version events from every project on the site.

    Payload del evento

    • versionobjectObligatorio

      The version the event is about.

    Version ReleasedJIRA_VERSION_RELEASEDTrigger

    Triggers when a project version is marked released.

    Configuración

    • project_idinteger

      Only fire for versions in this Jira project, given as the NUMERIC project id (e.g. 10705). A version event carries only the id and never the project key. Call JIRA_GET_ALL_PROJECTS with query='<your project key or name>' and take the 'id' off the result. Leave unset to receive version events from every project on the site.

    Payload del evento

    • versionobjectObligatorio

      The version the event is about.

    Version UnreleasedJIRA_VERSION_UNRELEASEDTrigger

    Triggers when a released project version is put back to unreleased.

    Configuración

    • project_idinteger

      Only fire for versions in this Jira project, given as the NUMERIC project id (e.g. 10705). A version event carries only the id and never the project key. Call JIRA_GET_ALL_PROJECTS with query='<your project key or name>' and take the 'id' off the result. Leave unset to receive version events from every project on the site.

    Payload del evento

    • versionobjectObligatorio

      The version the event is about.

    Version UpdatedJIRA_VERSION_UPDATEDTrigger

    Triggers when a project version's name, description or dates change. Releasing and un-releasing a version each fire this as well, alongside Version Released and Version Unreleased.

    Configuración

    • project_idinteger

      Only fire for versions in this Jira project, given as the NUMERIC project id (e.g. 10705). A version event carries only the id and never the project key. Call JIRA_GET_ALL_PROJECTS with query='<your project key or name>' and take the 'id' off the result. Leave unset to receive version events from every project on the site.

    Payload del evento

    • versionobjectObligatorio

      The version the event is about.