Jira Ticket State Polling
This Playbook is part of the Atlassian Jira Pack.#
Supported versions
Supported Cortex XSOAR versions: 6.0.0 and later.
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.
Dependencies#
This playbook uses the following sub-playbooks, integrations, and scripts.
Sub-playbooks#
This playbook does not use any sub-playbooks.
Integrations#
This playbook does not use any integrations.
Scripts#
- RunPollingCommand
- PrintErrorEntry
- ScheduleGenericPolling
Commands#
This playbook does not use any commands.
Playbook Inputs#
| Name | Description | Default Value | Required |
|---|---|---|---|
| TicketId | The Jira TicketId to poll for its state. | Required | |
| Interval | Frequency that the polling command will run (minutes). | Required | |
| Timeout | Amount of time to poll before declaring a timeout and resuming the playbook (in minutes). | Required | |
| InstanceName | Set the Jira Instance that will be used by the polling command. Only relevant when there is more than one Jira instance. | Optional | |
| AdditionalPollingCommandName | 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. When implemented, add "Using" to the value. The polling command will then take the instance name as the instance to use. | Optional |
Playbook Outputs#
There are no outputs for this playbook.
Playbook Image#
