Jira Inbound Integration

Jira is a project and issue tracking platform used by software teams to manage tasks, bugs, and feature work. It supports native webhooks that fire whenever an issue is created, updated, or deleted — making it straightforward to forward those events to ITOC360 in real time.

This integration creates an alert in ITOC360 whenever a Jira issue is opened or moved to an active status, and automatically resolves it when the issue is marked as Done, closed, or resolved.

How It Works

Jira sends an HTTP POST request to your ITOC360 webhook URL every time a subscribed issue event occurs. The payload includes the full issue details — summary, status, priority, and the user who triggered the change. ITOC360 uses the issue's status to decide whether to open or resolve an alert, and uses the issue key (e.g. KAN-5) as the fingerprint to match events belonging to the same issue together.

Prerequisites

• A Jira Cloud account with admin access

• Your ITOC360 webhook URL, generated when you create the source

In ITOC360

Go to Sources, click Create Source, and select Jira from the list. Copy the webhook URL that appears — you'll need it in the next steps.

In Jira

Step 1 — Open System Settings

Click the gear icon in the top right corner of Jira, then select System from the settings menu.

In the left sidebar, scroll down to the Advanced section and click WebHooks.

Step 2 — Create a Webhook

On the WebHooks page, click + Create a WebHook in the top right corner.

Fill in the form as follows:

• Name — give it a recognizable name like itoc360

• Status — leave as Enabled

• URL — paste your ITOC360 webhook URL here

• Secret — leave blank

  

---

Step 3 — Select Events

Scroll down to the Issue section and check created, updated, and deleted. Leave the JQL field set to All issues unless you want to scope the webhook to a specific project.

Click Create to save.

Alert Behavior

Event	itoc360 Action
Issue created	Opens an alert
Issue updated → status becomes Done / Closed / Resolved	Resolves the alert
Issue deleted	Resolves the alert
Issue updated → any other change	Opens or updates the alert

The alert priority is mapped from the Jira issue priority field.

Jira Priority	itoc360 Priority
Critical	CRITICAL
High	HIGH
Medium	MEDIUM
Low	LOW

Notes

• ITOC360 uses the Jira issue key (e.g. KAN-5) as the unique fingerprint. If the same issue transitions through multiple statuses, all events are grouped under the same alert.

• If you want to limit notifications to a specific project, add a JQL filter like project = KAN in the webhook configuration.

• You can create multiple webhooks pointing to different ITOC360 sources if you want to separate alerts by project or team.