Issue Event

Connection

Configuration

3 fields, none required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "allow_unsigned": false,
  "events": [
    "jira:issue_created",
    "jira:issue_updated"
  ],
  "jql_filter": "project = ENG AND issuetype = Bug"
}

Output

One shape.

{
  "changelog": [],
  "changelog_id": "",
  "comment": {
    "author": {
      "accountId": "",
      "displayName": "",
      "emailAddress": ""
    },
    "body": "",
    "created": "",
    "id": "",
    "updated": ""
  },
  "issue": {
    "assignee": {
      "accountId": "",
      "displayName": "",
      "emailAddress": ""
    },
    "id": "",
    "issue_type": "",
    "key": "ENG-412",
    "labels": [],
    "priority": "",
    "project": {
      "id": "",
      "key": "ENG",
      "name": ""
    },
    "reporter": {
      "accountId": "",
      "displayName": "",
      "emailAddress": ""
    },
    "status": "",
    "status_category": "",
    "summary": "",
    "url": ""
  },
  "issue_event_type_name": "issue_updated",
  "payload": {},
  "timestamp": 0,
  "user": {
    "accountId": "",
    "displayName": "",
    "emailAddress": ""
  },
  "webhookEvent": "jira:issue_updated",
  "worklog": {
    "author": {
      "accountId": "",
      "displayName": "",
      "emailAddress": ""
    },
    "comment": "",
    "id": "",
    "started": "",
    "time_spent": "",
    "time_spent_seconds": 0
  }
}

Notes

• Mantle creates the webhook in Jira when the workflow is published and deletes it when the workflow is unpublished, disabled or archived — do not add it by hand.
• The connection's account must be a Jira administrator: registering a webhook is an admin operation, and publish fails with Jira's own message if it is not.
• Deliveries are signed. Mantle generates a random secret, registers it, and verifies the X-Hub-Signature HMAC over the raw body; a bad signature is refused before any run starts.
• If your site does not confirm signing (no isSigned on registration) the webhook is deleted again and the publish fails, rather than leaving an unauthenticated URL armed. Tick allow_unsigned to accept URL-only authentication anyway — then anyone who learns the callback URL can start runs.
• jql_filter and events are applied when the workflow is published, so they cannot use {{ }} expressions — there is no run to evaluate them against.
• Jira sends no delivery id. Runs are deduped on webhookEvent + issue id + timestamp + the change-group / comment / worklog id, so a Jira retry cannot start a second run.
• MANTLE_APP_PUBLIC_BASE_URL must be a public https:// URL — Jira refuses to register a plain-http or unreachable callback.

Related Jira nodes

• Add Attachment
• Add Comment
• Add Watcher
• Assign Issue
• Count Issues
• Create Issue
• Create Sprint
• Delete Comment