Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jira v2 deprecated #29649

Merged
merged 6 commits into from
Sep 13, 2023
Merged

Jira v2 deprecated #29649

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
a5c9f9c
Deprecate to jira v2
israelpoli Sep 13, 2023
190be86
update RN
israelpoli Sep 13, 2023
6a812ef
update conf.json file
israelpoli Sep 13, 2023
42b95e3
add task to the Create Jira Issue playbook that check if jira v3 is e…
israelpoli Sep 13, 2023
e51c559
add image.png of the playbook
israelpoli Sep 13, 2023
faa97f7
update the playbook (yml, readme, image) and RN
israelpoli Sep 13, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions Packs/Jira/Integrations/JiraV2/JiraV2.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,7 @@ category: Case Management
commonfields:
id: jira-v2
version: -1
deprecated: true
configuration:
- display: 'Jira URL, for example: https://demisto.atlassian.net/'
name: url
Expand Down Expand Up @@ -116,8 +117,8 @@ configuration:
name: incidentFetchInterval
type: 19
required: false
description: Use the Jira integration to manage issues, create Cortex XSOAR incidents from Jira projects, and mirror issues to existing issue incidents in Cortex XSOAR.
display: Atlassian Jira v2
description: Deprecated. Use the Atlassian Jira v3 integration instead
display: Atlassian Jira v2 (Deprecated)
name: jira-v2
script:
commands:
Expand Down
148 changes: 95 additions & 53 deletions Packs/Jira/Playbooks/playbook-Create_Jira_Issue.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,15 +3,7 @@ version: -1
contentitemexportablefields:
contentitemfields: {}
name: Create Jira Issue
description: "Create Jira issue allows you to open new issues.\nWhen 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.\nAlternatively, 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:\
\ \n1. StatePolling\n2. Mirror\n3. Leave Blank to use none\n\nWhen 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!=)."
description: "Create Jira issue allows you to open new issues.\nWhen 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.\nAlternatively, 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: \n1. StatePolling\n2. Mirror\n3. Leave Blank to use none\n\nWhen 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!=)."
starttaskid: "0"
tasks:
"0":
Expand All @@ -33,14 +25,17 @@ tasks:
{
"position": {
"x": 50,
"y": -430
"y": 10
}
}
note: false
timertriggers: []
ignoreworker: false
skipunavailable: false
quietmode: 0
continueonerrortype: ""
isoversize: false
isautoswitchedtoquietmode: false
"3":
id: "3"
taskid: e764c3a4-f26b-47ee-82e9-1e33da961f15
Expand Down Expand Up @@ -79,15 +74,18 @@ tasks:
view: |-
{
"position": {
"x": 750,
"y": 40
"x": 50,
"y": 545
}
}
note: false
timertriggers: []
ignoreworker: false
skipunavailable: false
quietmode: 0
continueonerrortype: ""
isoversize: false
isautoswitchedtoquietmode: false
"8":
id: "8"
taskid: 50ecfc72-0d3f-4d2e-8f12-d5c7b5627d76
Expand All @@ -104,15 +102,18 @@ tasks:
view: |-
{
"position": {
"x": 50,
"y": 1170
"x": 370,
"y": 1245
}
}
note: false
timertriggers: []
ignoreworker: false
skipunavailable: false
quietmode: 0
continueonerrortype: ""
isoversize: false
isautoswitchedtoquietmode: false
"9":
id: "9"
taskid: bcb3872c-e94b-47df-87e0-0104d51ebeeb
Expand Down Expand Up @@ -159,15 +160,18 @@ tasks:
view: |-
{
"position": {
"x": 750,
"y": 585
"x": 50,
"y": 895
}
}
note: false
timertriggers: []
ignoreworker: false
skipunavailable: false
quietmode: 0
continueonerrortype: ""
isoversize: false
isautoswitchedtoquietmode: false
"13":
id: "13"
taskid: f2d4551f-8dd6-43d3-8850-57a1acf773e1
Expand All @@ -176,8 +180,7 @@ tasks:
id: f2d4551f-8dd6-43d3-8850-57a1acf773e1
version: -1
name: Mirror Jira Ticket
description: Mirror Jira Ticket is designed to serve as a sub-playbook, which
enables ticket mirroring with Jira.
description: Mirror Jira Ticket is designed to serve as a sub-playbook, which enables ticket mirroring with Jira.
playbookName: Mirror Jira Ticket
type: playbook
iscommand: false
Expand Down Expand Up @@ -217,15 +220,18 @@ tasks:
view: |-
{
"position": {
"x": 290,
"y": 770
"x": 50,
"y": 1070
}
}
note: false
timertriggers: []
ignoreworker: false
skipunavailable: false
quietmode: 0
continueonerrortype: ""
isoversize: false
isautoswitchedtoquietmode: false
"14":
id: "14"
taskid: d513362a-1605-4e4e-8b90-07c1d82f8310
Expand Down Expand Up @@ -270,15 +276,18 @@ tasks:
view: |-
{
"position": {
"x": 1190,
"y": 770
"x": 680,
"y": 1070
}
}
note: false
timertriggers: []
ignoreworker: false
skipunavailable: false
quietmode: 0
continueonerrortype: ""
isoversize: false
isautoswitchedtoquietmode: false
"15":
id: "15"
taskid: d1b67f95-6ce5-4ed5-8c45-e51b53567b2d
Expand Down Expand Up @@ -306,8 +315,8 @@ tasks:
view: |-
{
"position": {
"x": 750,
"y": 320
"x": 50,
"y": 720
}
}
note: false
Expand Down Expand Up @@ -375,23 +384,25 @@ tasks:
accessor: Key
skipunavailable: false
quietmode: 0
continueonerrortype: ""
isoversize: false
isautoswitchedtoquietmode: false
"16":
id: "16"
taskid: a253cb13-345f-4190-892d-6064744317ef
taskid: ca2e71b9-1850-4702-8421-4977e9cbc876
type: condition
task:
id: a253cb13-345f-4190-892d-6064744317ef
id: ca2e71b9-1850-4702-8421-4977e9cbc876
version: -1
name: Is Jira integration enabled?
description: Returns 'yes' if integration brand is available. Otherwise returns
'no'
name: Is Jira V2 integration enabled?
description: Returns 'yes' if integration brand is available. Otherwise returns 'no'
scriptName: IsIntegrationAvailable
type: condition
iscommand: false
brand: ""
nexttasks:
"no":
- "8"
- "17"
"yes":
- "3"
scriptarguments:
Expand All @@ -404,27 +415,71 @@ tasks:
{
"position": {
"x": 50,
"y": -240
"y": 185
}
}
note: false
timertriggers: []
ignoreworker: false
skipunavailable: false
quietmode: 0
continueonerrortype: ""
isoversize: false
isautoswitchedtoquietmode: false
"17":
id: "17"
taskid: 7133c080-325b-4a45-85e2-e9fd1a6b38ca
type: condition
task:
id: 7133c080-325b-4a45-85e2-e9fd1a6b38ca
version: -1
name: Is Jira V3 integration enabled?
description: Returns 'yes' if integration brand is available. Otherwise returns 'no'
scriptName: IsIntegrationAvailable
type: condition
iscommand: false
brand: ""
nexttasks:
"no":
- "8"
"yes":
- "3"
scriptarguments:
brandname:
simple: Jira V3
results:
- brandInstances
separatecontext: false
continueonerrortype: ""
view: |-
{
"position": {
"x": 370,
"y": 370
}
}
note: false
timertriggers: []
ignoreworker: false
skipunavailable: false
quietmode: 0
isoversize: false
isautoswitchedtoquietmode: false
system: true
view: |-
{
"linkLabelsPosition": {
"16_3_yes": 0.52,
"9_14_State Polling": 0.52
"17_8_no": 0.27,
"9_14_State Polling": 0.64,
"9_8_#default#": 0.55
},
"paper": {
"dimensions": {
"height": 1665,
"width": 1520,
"height": 1300,
"width": 1010,
"x": 50,
"y": -430
"y": 10
}
}
}
Expand Down Expand Up @@ -452,13 +507,7 @@ inputs:
- key: SyncTicket
value: {}
required: false
description: "Set the value of the desired sync method with Jira Issue. you can\
\ choose one of three options:\n1. StatePolling\n2. Mirror \n3. Blank for none\
\ \n\nGenericPolling polls for the state of the ticket and runs until the ticket\
\ state is either resolved or closed. \n\nMirror - You can use the Mirror option\
\ to perform a full sync with the Jira Ticket. The ticket data is synced automatically\
\ between Jira and Cortex xSOAR with the Jira mirror feature.\nIf this option\
\ is selected, FieldPolling is true by default. "
description: "Set the value of the desired sync method with Jira Issue. you can choose one of three options:\n1. StatePolling\n2. Mirror \n3. Blank for none \n\nGenericPolling polls for the state of the ticket and runs until the ticket state is either resolved or closed. \n\nMirror - You can use the Mirror option to perform a full sync with the Jira Ticket. The ticket data is synced automatically between Jira and Cortex xSOAR with the Jira mirror feature.\nIf this option is selected, FieldPolling is true by default. "
playbookInputQuery:
- key: PollingInterval
value: {}
Expand All @@ -477,11 +526,7 @@ inputs:
- key: AdditionalPollingCommandName
value: {}
required: false
description: "In this use case, Additional polling commands are relevant when using\
\ StatePolling, and there is more than one Jira instance. It will specify the\
\ polling command to use a specific instance to run on. \nIf so, please add \"\
Using\" to the value. \nThe playbook will then take the instance name as the instance\
\ to use. "
description: "In this use case, Additional polling commands are relevant when using StatePolling, and there is more than one Jira instance. It will specify the polling command to use a specific instance to run on. \nIf so, please add \"Using\" to the value. \nThe playbook will then take the instance name as the instance to use. "
playbookInputQuery:
- key: InstanceName
value: {}
Expand All @@ -493,16 +538,13 @@ inputs:
value:
simple: Both
required: false
description: "Set the mirror direction, should be one of the following: \n1. In\n\
2. Out\n3. Both"
description: "Set the mirror direction, should be one of the following: \n1. In\n2. Out\n3. Both"
playbookInputQuery:
- key: MirrorTags
value:
simple: comment,attachment
required: false
description: "Set tags for mirror comments and files to Jira.\nAs defined in the\
\ instance settings, by default it will be comment for comments mirroring and\
\ attachment for attachments mirroring. "
description: "Set tags for mirror comments and files to Jira.\nAs defined in the instance settings, by default it will be comment for comments mirroring and attachment for attachments mirroring. "
playbookInputQuery:
- key: FieldPolling
value: {}
Expand All @@ -520,5 +562,5 @@ inputs:
playbookInputQuery:
outputs: []
tests:
- Jira-v2-Test
- No test.
fromversion: 6.0.0
Loading