Skip to main content
Skip table of contents

ServiceNow incidents to Jira tasks

Use Case

Requirements

#

ServiceNow

Jira

Connected Systems

Authentication (supported methods)

  • Username and Password

  • Username and Password (server)

  • Username and API Token (cloud)

Permissions

  • incident (READ, WRITE, CREATE)

  • sys_db_object (READ)

  • sys_dictionary (READ)

  • sys_journal_field (READ)

  • sys_glide_object (READ)

  • Add Comments

  • Assign issues

  • Browse Projects

  • Create Attachments

  • Create Issues

  • Edit Issues

  • Resolve Issues

  • Transition issues

Environment

  • Integration User:

    • Timezone → “GMT”

    • Date Format → “yyyy-MM-dd”

    • User ID → Same as the “Username”

  • Correlation Field

  • API Token (cloud)

Network (default port)

  • ZigiOps → ServiceNow (80/443)

  • ZigiOps → Jira (80/443)

Network Requirements

Setup

  1. Log in to your ZigiOps instance.

  2. Go to ZigiOps → Configurator and load the integration template.

  3. Select the desired Integrated Systems and Integrated Systems and click the Save button to continue.

  4. Enable the integration from the Slider button located in the middle section of the screen.

How does the Jira ServiceNow Integration work?

  1. When there is a new incident in ServiceNow, ZigiOps will automatically collect it, based on a predefined time interval, and transfer it to Jira as a task. All necessary fields will be transformed and also moved to Jira (based on the defined mapping in ZigiOps).

  2. Once there is an update on the ServiceNow incident, ZigiOps will pick it up and populate the corresponding Jira task with the necessary fields (comments, attachments, assignees, and more).

  3. When the Jira task is closed or updated, ZigiOps will close or update the corresponding ServiceNow incident with the applicable information or close the incident.

Specifics

No specifics are available for this integration.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.