Jira Trigger

Overview

The Jira trigger fires your procedure when issues, comments, or sprints change in your Jira instance — for example when a bug is created, an issue is transitioned, or a sprint starts.

Setup

Go to Connections in the Rapidfolio dashboard and connect your Jira instance.
Open the procedure you want to trigger and add a Jira trigger.
Select the event types and optional project filters, then save the trigger.
Copy the generated webhook URL and register it in your Jira instance under Settings → System → WebHooks → Create a WebHook.

Webhook URL

https://run.rapidfolio.com/triggers/:triggerId/jira

Replace :triggerId with the trigger ID shown in the Rapidfolio dashboard.

Signature Verification

Rapidfolio verifies inbound Jira webhook requests using a shared secret. When registering the webhook in Jira, add the secret as a query parameter — Rapidfolio will handle verification automatically.

Configuration

Field	Description
Connection	The Jira connection
Projects	Filter to specific project keys (optional) — e.g. `ENG`, `OPS`
Event types	One or more Jira event types to subscribe to (see below)
Issue types	Filter to specific issue types — e.g. `Bug`, `Story`, `Epic` (optional)

Supported Event Types

Issue Events

Event type	Description
`jira:issue_created`	A new issue was created
`jira:issue_updated`	An issue was updated (status, assignee, summary, etc.)
`jira:issue_deleted`	An issue was deleted

Comment Events

Event type	Description
`comment_created`	A comment was added to an issue
`comment_updated`	A comment was edited
`comment_deleted`	A comment was deleted

Sprint Events

Event type	Description
`sprint_created`	A new sprint was created
`sprint_updated`	A sprint was updated
`sprint_started`	A sprint was started
`sprint_closed`	A sprint was closed

Version Events

Event type	Description
`jira:version_created`	A new version (fix version) was created
`jira:version_released`	A version was marked as released

Payload

The trigger payload is the Jira webhook event body. Access it via the trigger input in your procedure.

Issue created

{
  "webhookEvent": "jira:issue_created",
  "timestamp": 1710500000000,
  "user": {
    "accountId": "5b10ac8d82e05b22cc7d4ef5",
    "displayName": "Alice Johnson",
    "emailAddress": "alice@example.com"
  },
  "issue": {
    "id": "10001",
    "key": "ENG-42",
    "fields": {
      "summary": "Implement new feature",
      "issuetype": { "name": "Story" },
      "status": { "name": "To Do" },
      "priority": { "name": "High" },
      "assignee": {
        "accountId": "5b10ac8d82e05b22cc7d4ef5",
        "displayName": "Alice Johnson"
      },
      "project": {
        "key": "ENG",
        "name": "Engineering"
      }
    }
  }
}

Issue updated

{
  "webhookEvent": "jira:issue_updated",
  "timestamp": 1710500500000,
  "changelog": {
    "items": [
      {
        "field": "status",
        "fromString": "To Do",
        "toString": "In Progress"
      }
    ]
  },
  "issue": {
    "id": "10001",
    "key": "ENG-42",
    "fields": {
      "summary": "Implement new feature",
      "status": { "name": "In Progress" }
    }
  }
}

The changelog.items array lists every field that changed and its previous value. Use this to detect specific transitions — for example, only proceeding when status changes to "Done".

Example Use Cases

Trigger an automated regression test suite when a Jira issue is transitioned to "In Review".
Send a Slack notification to the ops channel when a Bug issue with priority: Critical is created.
Start a compliance review workflow when a jira:issue_created event arrives in the COMPLIANCE project.
Log sprint velocity metrics to your data warehouse when sprint_closed fires.