Atlassian Jira

Details
Content
Dependencies
Version History

Use the Jira integration to manage issues and create Cortex XSOAR incidents from Jira projects.

This pack enables you to manage issues in Jira and exchange information between Jira and Cortex XSOAR.

What does this pack do?

This pack enables you to

Create, edit, delete, and query Jira issues.
Add information to Jira issues in the form of links, comments, and attachments.
Get information concerning boards, and sprints.
Create Cortex XSOAR incidents from Jira issues.
Mirror information from Jira to Cortex XSOAR and vice versa.

The pack includes the Atlassian Jira v2, and Atlassian Jira v3 integration, the Jira Incident, and JiraV3 Incident incident type, incident fields, incident layouts to display all of the Jira information, and 6 scripts:

JiraCreateIssue-example: Simplifies the process of creating a new issue in Jira.
JIRAPrintIssue: Prints a Jira issue in the War Room.
script-JiraChangeTransition: Gets the new Jira status and updates the Cortex XSOAR incident status by applying a transition.
script-JiraListTransition: Lists all possible transitions for a given issue.
script-JiraChangeStatus: Gets the new Jira status and updates the Cortex XSOAR incident status by choosing a specific status.
script-JiraListStatus: Lists all possible statuses for a given issue.

How does this pack work?

Create an instance of the Atlassian Jira v2, or Atlassian Jira v3 integration and start fetching and ingesting incidents.

Pack Contributors:

Paul-Adrian Dragoi

Contributions are welcome and appreciated. For more info, visit our Contribution Guide.

This pack enables you to manage issues in Jira and exchange information between Jira and Cortex XSOAR.

What does this pack do?

This pack enables you to

Create, edit, delete, and query Jira issues.
Add information to Jira issues in the form of links, comments, and attachments.
Get information concerning boards, and sprints.
Create Cortex XSOAR incidents from Jira issues.
Mirror information from Jira to Cortex XSOAR and vice versa.

JiraCreateIssue-example: Simplifies the process of creating a new issue in Jira.
JIRAPrintIssue: Prints a Jira issue in the War Room.
script-JiraChangeTransition: Gets the new Jira status and updates the Cortex XSOAR incident status by applying a transition.
script-JiraListTransition: Lists all possible transitions for a given issue.
script-JiraChangeStatus: Gets the new Jira status and updates the Cortex XSOAR incident status by choosing a specific status.
script-JiraListStatus: Lists all possible statuses for a given issue.

How does this pack work?

Create an instance of the Atlassian Jira v2, or Atlassian Jira v3 integration and start fetching and ingesting incidents.

Pack Contributors:

Paul-Adrian Dragoi

Contributions are welcome and appreciated. For more info, visit our Contribution Guide.

Automations

Name	Description
JiraCreateIssue-example	This script is used to simplify the process of creating a new Issue in Jira. You can specify custom fields using the `customFields` argument.
JiraV3ConvertSubtasksToTable	This script is used to convert Jira subtasks to a table.
JiraListStatus	This script lists all possible statuses for a given Jira issue. Works only for Jira v3.
JiraAddComment	Use this script to add a comment with a tag (the "Comment tag to Jira" defined in the instance configuration) as an entry in XSOAR, which will then be mirrored as a comment to a Jira issue. This script should be run within an incident.
JiraV3ConvertCommentsToTable	This script is used to convert Jira comments to a table.
JiraChangeStatus	This script changes the status field of a Jira incident. It gets the new Jira status of the remote Jira issue and updates the Cortex XSOAR incident status.
script-JiraChangeTransition	This script applies the transition supplied by the user from the Jira Transitions incident field. It gets the new Jira status after applying the transition and updates the Cortex XSOAR incident status.
JIRAPrintIssue	Pretty print JIRA issue into the incident war room
JiraV3ConvertAttachmentsToTable	This script is used to convert Jira attachments to a table.
script-JiraListTransition	This script lists all possible transitions for a given Jira issue.

Classifiers

Name	Description
classifier-mapper-outgoing-Jira	Jira V2 mirror out classifier.
classifier-mapper-incoming-JiraV3	Jira V3 mirror in classifier.
classifier-mapper-incoming-JiraV2	Jira V2 mirror in classifier.
JiraV3 Outgoing Mapper

Incident Fields

Name	Description
Jira Reporter Name
Jira Transitions
Jira Project	The Jira project where the issue resides in.
Jira Component	The components of a Jira issue.
Jira Due Date	The due date for the issue (in the format 2018-03-11)
Jira Issue Type	The issue type of the Jira issue.
Jira Description	This issue's description
Jira Status	The name of the status
Jira ID
Jira Priority	The issue's priority
Jira Reporter Email
Jira Labels
Jira Subtask	The subtasks of a Jira issue.
Jira Comment	The comments returned from a Jira issue.
Jira Issue Key
Jira Summary	The issue's summary
JiraV3 Status	This will show the current status of the Jira issue, and when pressed, a list of possible statuses will be shown.
Created Time
Jira Attachments
Jira Estimate	The estimated timeline of a Jira issue in seconds. Please take a look at your `Time tracking settings` in Jira to identify what is considered an hour and a week.

Incident Types

Name	Description
Jira Create Issue and Mirror
Jira Incident
JiraV3 Incident

Integrations

Name	Description
Atlassian Jira v2 (Deprecated)	Deprecated. Use the Atlassian Jira v3 integration instead
Atlassian 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.

Layouts

Name	Description
JiraV3 Incident Layout
Jira Incident Layout

Playbooks

Name	Description
Jira Ticket State Polling	Use Jira Incident State Polling as a sub-playbook when required to pause the execution of a master playbook until the Jira ticket state is either resolved or closed. This playbook implements polling by continuously running the jira-get-issue command until the state is either resolved or closed.
Create Jira Issue	Create Jira issue allows you to open new issues. When creating the issue, you can decide to update based on on the issue's state, which will wait for the issue to resolve or close with StatePolling. Alternatively, you can select to mirror the Jira issue and incident fields. To apply either of these options, set the SyncTicket value in the playbook inputs to one of the following options: StatePolling Mirror Leave Blank to use none When creating Jira issues through XSOAR, using the mirroring function, make sure that you exclude those issues when fetching incidents. To exclude these issues, tag the relevant issues with a dedicated label and exclude that label from the JQL query (Labels!=).
Mirror Jira Ticket	Mirror Jira Ticket is designed to serve as a sub-playbook, which enables ticket mirroring with Jira.

Automations

Name	Description
JiraV3ConvertSubtasksToTable	This script is used to convert Jira subtasks to a table.
JiraChangeStatus	This script changes the status field of a Jira incident. It gets the new Jira status of the remote Jira issue and updates the Cortex incident status.
JIRAPrintIssue	Pretty print JIRA issue into the incident war room
JiraAddComment	Use this script to add a comment with a tag (the "Comment tag to Jira" defined in the instance configuration) as an entry in XSOAR, which will then be mirrored as a comment to a Jira issue. This script should be run within an incident.
script-JiraChangeTransition	This script applies the transition supplied by the user from the Jira Transitions incident field. It gets the new Jira status after applying the transition and updates the Cortex incident status.
JiraListStatus	This script lists all possible statuses for a given Jira issue. Works only for Jira v3.
JiraCreateIssue-example	This script is used to simplify the process of creating a new Issue in Jira. You can specify custom fields using the `customFields` argument.
script-JiraListTransition	This script lists all possible transitions for a given Jira issue.
JiraV3ConvertAttachmentsToTable	This script is used to convert Jira attachments to a table.
JiraV3ConvertCommentsToTable	This script is used to convert Jira comments to a table.

Classifiers

Name	Description
JiraV3 Outgoing Mapper
classifier-mapper-incoming-JiraV3	Jira V3 mirror in classifier.
classifier-mapper-incoming-JiraV2	Jira V2 mirror in classifier.
classifier-mapper-outgoing-Jira	Jira V2 mirror out classifier.

Incident Fields

Name	Description
JiraV3 Status	This will show the current status of the Jira issue, and when pressed, a list of possible statuses will be shown.
Jira Estimate	The estimated timeline of a Jira issue in seconds. Please take a look at your `Time tracking settings` in Jira to identify what is considered an hour and a week.
Jira Component	The components of a Jira issue.
Jira Reporter Name
Jira Labels
Jira Project	The Jira project where the issue resides in.
Jira Transitions
Jira Status	The name of the status
Jira Comment	The comments returned from a Jira issue.
Jira Summary	The issue's summary
Jira ID
Jira Issue Type	The issue type of the Jira issue.
Jira Priority	The issue's priority
Jira Issue Key
Jira Due Date	The due date for the issue (in the format 2018-03-11)
Jira Subtask	The subtasks of a Jira issue.
Jira Reporter Email
Jira Attachments
Jira Description	This issue's description

Incident Types

Name	Description
Jira Create Issue and Mirror
Jira Incident
JiraV3 Incident

Integrations

Name	Description
Jira Event Collector	Jira logs event collector integration for Cortex XSIAM.
Atlassian Jira v2 (Deprecated)	Deprecated. Use the Atlassian Jira v3 integration instead
Atlassian Jira v3	Use the Jira integration to manage issues, create Cortex incidents from Jira projects, and mirror issues to existing issue incidents in Cortex. The integration now supports both OnPrem, and Cloud instances.

Modeling Rules

Name	Description
JiraEventCollector

Parsing Rules

Name	Description
Jira Parsing Rule

Playbooks

Name	Description
Create Jira Issue	Create Jira issue allows you to open new issues. When creating the issue, you can decide to update based on on the issue's state, which will wait for the issue to resolve or close with StatePolling. Alternatively, you can select to mirror the Jira issue and incident fields. To apply either of these options, set the SyncTicket value in the playbook inputs to one of the following options: StatePolling Mirror Leave Blank to use none When creating Jira issues through XSOAR, using the mirroring function, make sure that you exclude those issues when fetching incidents. To exclude these issues, tag the relevant issues with a dedicated label and exclude that label from the JQL query (Labels!=).
Mirror Jira Ticket	Mirror Jira Ticket is designed to serve as a sub-playbook, which enables ticket mirroring with Jira.
Jira Ticket State Polling	Use Jira Incident State Polling as a sub-playbook when required to pause the execution of a master playbook until the Jira ticket state is either resolved or closed. This playbook implements polling by continuously running the jira-get-issue command until the state is either resolved or closed.

Required Content Packs (3)

Pack Name	Pack By
Base	By: Cortex XSOAR
Common Playbooks	By: Cortex XSOAR
Common Scripts	By: Cortex XSOAR

Optional Content Packs (1)

Pack Name	Pack By
Common Types	By: Cortex XSOAR

All level dependencies (6)

Pack Name	Pack By
Rasterize	By: Cortex XSOAR
Cortex REST API	By: Cortex XSOAR
Common Playbooks	By: Cortex XSOAR
Base	By: Cortex XSOAR
Filters And Transformers	By: Cortex XSOAR
Common Scripts	By: Cortex XSOAR

3.2.10 - R1834150 (December 18, 2024)

Scripts

JiraListStatus

Updated the Docker image to: demisto/python3:3.11.10.115186.

script-JiraChangeTransition

Updated the Docker image to: demisto/python3:3.11.10.115186.

JiraV3ConvertCommentsToTable

Updated the Docker image to: demisto/python3:3.11.10.115186.

JiraChangeStatus

Updated the Docker image to: demisto/python3:3.11.10.115186.

JiraCreateIssue-example

Updated the Docker image to: demisto/python3:3.11.10.115186.

JiraV3ConvertAttachmentsToTable

Updated the Docker image to: demisto/python3:3.11.10.115186.

script-JiraListTransition

Updated the Docker image to: demisto/python3:3.11.10.115186.

JiraAddComment

Updated the Docker image to: demisto/python3:3.11.10.115186.

JiraV3ConvertSubtasksToTable

Updated the Docker image to: demisto/python3:3.11.10.115186.

Related pull requests:
- 37147
- 37137
- 37136
- 37140
- 37138
- 37139

Download

3.2.9 - 1621428 (November 11, 2024)

Integrations

Atlassian Jira v3

Updated the Docker image to: demisto/btfl-soup:1.0.1.115405.

Related pull requests:
- 37124
- 37111

Download

3.2.8 - 1619437 (November 10, 2024)

Changes are not relevant for XSOAR marketplace.

Related pull requests:
- 37059
- 37052
- 37051

Download

3.2.7 - 1507818 (October 14, 2024)

Integrations

Atlassian Jira v3

Added the following new commands:

jira-create-metadata-field-list.
jira-create-metadata-issue-types-list.

Related pull requests:
- 36613
- 36693

Download

3.2.6 - 1470320 (October 6, 2024)

Integrations

Atlassian Jira v3

Added the jira-issue-get-forms command for pulling down ProForma data.
Added the jira-get-user-info command for getting user information.
Included forms in fetch data.

Related pull requests:
- 35856
- 36604

Download

3.2.5 - 1436534 (September 26, 2024)

Integrations

Atlassian Jira v3

Updated the Docker image to: demisto/btfl-soup:1.0.1.111953.

Related pull requests:
- 36524

Download

3.2.4 - R1317860 (August 28, 2024)

Integrations

Atlassian Jira v3

Fixed an issue where the mirroring process recreated an attachment with any field change.
Updated the Docker image to: demisto/btfl-soup:1.0.1.107991.

Related pull requests:
- 35826

Download

3.2.3 - 1256255 (August 8, 2024)

Integrations

Atlassian Jira v3

Fixed an issue where the mirroring out process incorrectly parsed custom fields.

Related pull requests:
- 35790

Download

3.2.2 - R1189290 (July 18, 2024)

Integrations

Atlassian Jira v3

Updated the Docker image to: demisto/btfl-soup:1.0.1.101506.

Related pull requests:
- 35300

Download

3.2.1 - R1164474 (July 10, 2024)

Integrations

Atlassian Jira v3

Fixed an issue where mirroring new comments from Jira to XSOAR was not functioning correctly.
Updated the Docker image to: demisto/btfl-soup:1.0.1.101506.

Related pull requests:
- 35285

Download

3.2.0 - 1112736 (June 23, 2024)

Changes are not relevant for XSOAR marketplace.

Related pull requests:
- 34255

Download

3.1.16 - 1082615 (June 10, 2024)

Locked dependencies of the pack to ensure stability for versioned core packs. No changes in this release.

Related pull requests:
- 34804

Download

3.1.15 - R1051712 (May 28, 2024)

Atlassian Jira

Locked dependencies of the pack to ensure stability for versioned core packs. No changes in this release.

Related pull requests:
- 34212

Download

3.1.14 - 962639 (April 17, 2024)

Integrations

Atlassian Jira v3

Fixed an issue where the files that were uploaded to Jira were automatically classified as type application-type instead of their specific mime type.
Updated the Docker image to: demisto/btfl-soup:1.0.1.91405.

Related pull requests:
- 33746

Download

3.1.13 - 927547 (April 1, 2024)

Changes are not relevant for XSOAR marketplace.

Related pull requests:
- 33663

Download

3.1.12 - 909962 (March 24, 2024)

Integrations

Atlassian Jira v3

Added a new command jira-issue-delete-file to delete attachment file from an issue.
Updated the Docker image to: demisto/btfl-soup:1.0.1.89280.

Related pull requests:
- 33315

Download

3.1.11 - 898707 (March 18, 2024)

Integrations

Atlassian Jira v3

Documentation and metadata improvements.

Related pull requests:
- 33378

Download

3.1.10 - 824222 (February 13, 2024)

Integrations

Atlassian Jira v3

Updated the documentation for the issue_json argument in the jira-create-issue and jira-edit-issue commands.
Updated the jira-create-issue command. Will now fail when providing the issue_json argument with another argument.
Updated the jira-edit-issue command. Will now fail when providing the issue_json argument with another argument except status, transition, action, issue_id, and issue_key.
Updated the Docker image to: demisto/btfl-soup:1.0.1.87353.

Related pull requests:
- 32818

Download

3.1.9 - 778227 (January 22, 2024)

Atlassian Jira

Locked dependencies of the pack to ensure stability for versioned core packs. No changes in this release.

Related pull requests:
- 32331

Download

3.1.8 - 778086 (January 22, 2024)

Integrations

Atlassian Jira v3

Fixed an issue where the command jira-edit-issue could not apply a transition, or status, with other arguments in the same request.
Updated the Docker image to: demisto/btfl-soup:1.0.1.85862.

Related pull requests:
- 32041

Download

3.1.7 - 752611 (January 9, 2024)

Scripts

JiraV3ConvertCommentsToTable

Updated the Docker image to: demisto/python3:3.10.13.83255.

JiraCreateIssue-example

Updated the Docker image to: demisto/python3:3.10.13.83255.

JiraListStatus

Updated the Docker image to: demisto/python3:3.10.13.83255.

JiraV3ConvertSubtasksToTable

Updated the Docker image to: demisto/python3:3.10.13.83255.

JiraChangeStatus

Updated the Docker image to: demisto/python3:3.10.13.83255.

script-JiraChangeTransition

Updated the Docker image to: demisto/python3:3.10.13.83255.

script-JiraListTransition

Updated the Docker image to: demisto/python3:3.10.13.83255.

JiraV3ConvertAttachmentsToTable

Updated the Docker image to: demisto/python3:3.10.13.83255.

JiraAddComment

Updated the Docker image to: demisto/python3:3.10.13.83255.

Related pull requests:
- 32030

Download

PUBLISHER

PLATFORMS

Cortex XSOARCortex XSIAM

INFO

Certification	Certified	Read more
Supported By	Cortex
Created	September 24, 2020
Last Release	December 18, 2024

WORKS WITH THE FOLLOWING INTEGRATIONS:

DISCLAIMER

Content packs are licensed by the Publisher identified above and subject to the Publisher’s own licensing terms. Palo Alto Networks is not liable for and does not warrant or support any content pack produced by a third-party Publisher, whether or not such packs are designated as “Palo Alto Networks-certified” or otherwise. For more information, see the Marketplace documentation.