Jira V3

Use the Jira integration to manage issues, create Cortex XSOAR incidents from Jira projects, and mirror issues to existing issue incidents in Cortex XSOAR. The integration now supports both OnPrem, and Cloud instances.

Case Management · Atlassian Jira

Configuration parameters

  • server_url — Server URL (required)
  • basic_credentials — User name
  • cloud_id — Cloud ID
  • callback_url — Callback URL
  • credentials — Client ID
  • pat_credential — Personal Access Token
  • fetch_query — Query (in JQL) for fetching incidents
  • issue_field_to_fetch_from — Issue Field to fetch by
  • id_offset — Issue index to start fetching incidents from
  • first_fetch — Time range for initial data fetch
  • insecure — Trust any certificate (not secure)
  • proxy — Use system proxy settings
  • isFetch — Fetch incidents
  • incidentType — Incident type
  • close_incident — Close Mirrored XSOAR Incident
  • mirror_direction — Mirroring Direction
  • attachment_tag_to_jira — Attachment Entry Tag to Jira
  • attachment_tag_from_jira — Attachment Entry Tag from Jira
  • comment_tag_to_jira — Comment Entry Tag to Jira
  • comment_tag_from_jira — Comment Entry Tag from Jira
  • fetch_comments — Fetch comments
  • fetch_attachments — Fetch attachments
  • max_fetch — Max incidents per fetch

Commands (46)

  • get-mapping-fields

    Returns the list of fields to map in outgoing mirroring. This command is only used for debugging purposes.

  • get-modified-remote-data

    Get the list of incidents that were modified since the last update time. This method is used for debugging purposes. The get-modified-remote-data command is used as part of the Mirroring feature that was introduced in Cortex XSOAR version 6.1.

  • get-remote-data

    Get remote data from a remote incident. This method does not update the current incident, and should be used for debugging purposes only.

  • get-remote-data-preview

    Get remote data from a remote incident. This method does not update the current incident, and should be used for debugging purposes only.

  • jira-board-backlog-list

    Get issues from the backlog of a specific board. For Jira OnPrem, the board must be of type scrum.

  • jira-board-epic-list

    Get all epics from a specific board.

  • jira-board-issue-list

    Get all issues from a specific board.

  • jira-board-list

    Get board data. If board_id is given, then only the board that corresponds to the board_id is returned, otherwise, the the command will return boards that match the project_key_id, type, or board_name arguments.

  • jira-board-sprint-list

    Get all sprints of a specific board.

  • jira-create-issue

    Creates a new issue in Jira.

  • jira-create-issue-quick-action

    Creates a new issue in Jira.

  • jira-create-metadata-field-list

    Returns a page of field metadata for a specified project and issue type.

  • jira-create-metadata-issue-types-list

    Returns a page of issue type metadata for a specified project.

  • jira-delete-issue

    Deletes an issue in Jira. Issue's sub-tasks will also be deleted if there are any.

  • jira-edit-issue

    Modifies an issue in Jira. If the status or transition fields are given, then the other supplied fields should appear on the transition screen.

  • jira-epic-issue-list

    Get all issues that belong to an epic (Child Issues).

  • jira-get-comments

    Returns the comments added to a ticket.

  • jira-get-id-by-attribute

    Gets the account ID for a given user attribute.

  • jira-get-id-offset

    Returns the ID offset, which is the ID of the first issue that was created in the current Jira instance, or the ID of the first issue with respect to the given query argument if given. You can use its result as the initial ID when fetching incidents by the issue id field.

  • jira-get-issue

    Fetches an issue from Jira.

  • jira-get-specific-field

    Gets specific fields from a Jira issue and adds it to context dynamically.

  • jira-get-user-info

    Retrieves information about a specified Jira user. For on-prem instances, you should use the user's key and username to retrieve their details. For Cloud instances, user's `account_id` is required. If no identifier is supplied, information for the user the API credentials belong to is returned.

  • jira-issue-add-comment

    Adds a new comment to an existing Jira issue.

  • jira-issue-add-link

    Creates (or updates) an issue link.

  • jira-issue-assign

    Assigns an assignee to an existing issue.

  • jira-issue-delete-comment

    Delete a comment from an issue.

  • jira-issue-delete-file

    Delete an attachment from an issue.

  • jira-issue-edit-comment

    Edit a comment that is part of an issue.

  • jira-issue-get-attachment

    Download attachments for a specific issue (Will download a file to War Room).

  • jira-issue-get-forms

    Fetches questions and answers for forms tied to a Jira issue. This command requires Jira Service Desk, the ProForma plugin and an API user with `Service Desk Team` or higher permissions on the Jira project the forms are being pulled from.

  • jira-issue-link-type-get

    Returns a list of all issue link types.

  • jira-issue-list-fields

    This command returns the issue fields, both system and custom fields.

  • jira-issue-query

    Queries Jira issues.

  • jira-issue-to-backlog

    Moves issues to backlog. If the issues supplied are NOT part of a board that supports sprints, then the board_id argument is required. At most 50 issues may be moved at once.

  • jira-issue-to-board

    Moves issues from backlog to board, the command does not work with boards with sprints. At most 50 issues may be moved at once. This command is only supported for Jira Cloud instances.

  • jira-issue-to-issue-link

    Use this command to create a link between two issues.

  • jira-issue-upload-file

    Uploads a file attachment to an issue.

  • jira-list-transitions

    Lists all possible transitions for a given ticket in its current status.

  • jira-oauth-complete

    Use this command to complete the authorization process. After copying the authorization code found in the query parameter `code` of the callback URL, paste the value in the command as an argument to finish the process.

  • jira-oauth-start

    Use this command to start the authorization process. In order to authorize the instance, first run the command, and complete the process in the URL that is returned. You will then be redirected to the callback URL where you will copy the authorization code found in the query parameter `code`, and paste that value in the command `!jira-ouath-complete` as an argument to finish the process.

  • jira-oauth-test

    Use this command to test the connectivity of the Jira instance.

  • jira-reset-timezone-cache

    Clears the cached Jira user timezone used for fetching incidents and mirroring from the internal cache. Use if the timezone settings tied to the chosen authentication method were changed.

  • jira-sprint-issue-list

    Get all issues in a sprint.

  • jira-sprint-issue-move

    Moves issues to a sprint, for a given sprint ID. Issues can only be moved to open or active sprints. At most 50 issues may be moved at once.

  • jira-user-group-search

    Searches for users and groups in Jira that match the query string.

  • update-remote-system

    Updates the remote incident with local incident changes. This method is only used for debugging purposes and will not update the current incident.