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.

Atlassian Jira · 6 tasks · 5 inputs · 0 outputs

Inputs

  • TicketId — The Jira TicketId to poll for its state.
  • Interval — Frequency that the polling command will run (minutes).
  • Timeout — Amount of time to poll before declaring a timeout and resuming the playbook (in minutes).
  • InstanceName — Set the Jira Instance that will be used by the polling command. Only relevant when there is more than one Jira instance.
  • 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.

Flowchart

YES Start Start Schedule Ticket State Polling Task - ScheduleGenericPolling Schedule Ticket State Pol... ScheduleGenericPolling Waiting for Ticket State Polling to complete (Automated Task) Waiting for Ticket State ... Run Ticket State Polling Command - RunPollingCommand Run Ticket State Polling ... RunPollingCommand Done Done Scheduled Task Failed - PrintErrorEntry Scheduled Task Failed PrintErrorEntry