Jira

A Jira webhook delivers issue lifecycle events from Jira into Plural. After you configure the source once, you can attach it to one or more workbench triggers to start jobs based on issue changes.

This guide uses the Plural Console UI and Jira webhook management. For general webhook behavior and trigger configuration, see Webhooks.

Prerequisites

Before you begin, make sure you have:

• A Jira site (Jira Cloud, Jira Server, or Jira Data Center) with issues you want to monitor.
• Jira administrator permissions to create and manage webhooks in your Jira site.
• Permission in Plural Console to create a webhook source and configure workbench triggers.
• An HTTPS-accessible Plural deployment. Deliver the webhook over HTTPS to protect the signing secret in transit.

Capabilities

Jira webhooks deliver issue lifecycle events:

• Issue created — a new issue is created in the project.
• Issue updated — issue fields such as summary, description, status, assignee, priority, or custom fields are modified.
• Issue transitioned — the issue moves to a different workflow state.
• Issue resolved — the issue is marked as resolved or fixed.
• Issue reopened — a resolved or closed issue is reopened.
• Issue deleted — an issue is removed from the project.

Plural accepts Jira webhook payloads that include an issue key. The integration supports both Jira Server/Data Center (plain text descriptions) and Jira Cloud (Atlassian Document Format descriptions). Status mapping recognizes common workflow states: Done, Closed, and Resolved map to completed; Cancelled, Rejected, Won't Do, and Won't Fix map to cancelled; In Progress maps to in progress; all others default to open.

Inbound events are stored as issues in Plural and do not start a job until a workbench trigger matches the payload content. See Webhook triggers for binding events to workbenches.